On 2013-05-07 21:44, Paolo Bonzini wrote:
> Il 07/05/2013 20:00, Jan Kiszka ha scritto:
>> On 2013-05-07 16:17, Paolo Bonzini wrote:
>>> With this change, a FlatView can be used even after a concurrent
>>> update has replaced it. Because we do not have RCU, we use a
>>> mutex to protect the small
Il 07/05/2013 20:00, Jan Kiszka ha scritto:
> On 2013-05-07 16:17, Paolo Bonzini wrote:
>> With this change, a FlatView can be used even after a concurrent
>> update has replaced it. Because we do not have RCU, we use a
>> mutex to protect the small critical sections that read/write the
>> as->cur
On 2013-05-07 20:00, Jan Kiszka wrote:
> On 2013-05-07 16:17, Paolo Bonzini wrote:
>> With this change, a FlatView can be used even after a concurrent
>> update has replaced it. Because we do not have RCU, we use a
>> mutex to protect the small critical sections that read/write the
>> as->current_
On 2013-05-07 16:17, Paolo Bonzini wrote:
> With this change, a FlatView can be used even after a concurrent
> update has replaced it. Because we do not have RCU, we use a
> mutex to protect the small critical sections that read/write the
> as->current_map pointer. Accesses to the FlatView can be
With this change, a FlatView can be used even after a concurrent
update has replaced it. Because we do not have RCU, we use a
mutex to protect the small critical sections that read/write the
as->current_map pointer. Accesses to the FlatView can be done
outside the mutex.
If a MemoryRegion will b
