[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-ppc] [RFC v3 0/56] per-CPU locks
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [Qemu-ppc] [RFC v3 0/56] per-CPU locks |
|
Date: |
Fri, 19 Oct 2018 08:59:24 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 |
On 19/10/2018 03:05, Emilio G. Cota wrote:
> I'm calling this series a v3 because it supersedes the two series
> I previously sent about using atomics for interrupt_request:
> https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg02013.html
> The approach in that series cannot work reliably; using (locked) atomics
> to set interrupt_request but not using (locked) atomics to read it
> can lead to missed updates.
The idea here was that changes to protected fields are all followed by
kick. That may not have been the case, granted, but I wonder if the
plan is unworkable.
Paolo
- [Qemu-ppc] [RFC v3 10/56] ppc: convert to cpu_halted, (continued)
- Re: [Qemu-ppc] [RFC v3 0/56] per-CPU locks,
Paolo Bonzini <=