On Thu, Feb 18, 2016 at 5:25 PM, Alex Bennée wrote:
>
> alvise rigo writes:
>
>> On Wed, Feb 17, 2016 at 7:55 PM, Alex Bennée wrote:
>>>
>>> Alvise Rigo writes:
>>>
As for the RAM case, also the MMIO exclusive ranges have to be protected
by other CPU's accesses. In order to do that, w
alvise rigo writes:
> On Wed, Feb 17, 2016 at 7:55 PM, Alex Bennée wrote:
>>
>> Alvise Rigo writes:
>>
>>> As for the RAM case, also the MMIO exclusive ranges have to be protected
>>> by other CPU's accesses. In order to do that, we flag the accessed
>>> MemoryRegion to mark that an exclusive
On Wed, Feb 17, 2016 at 7:55 PM, Alex Bennée wrote:
>
> Alvise Rigo writes:
>
>> As for the RAM case, also the MMIO exclusive ranges have to be protected
>> by other CPU's accesses. In order to do that, we flag the accessed
>> MemoryRegion to mark that an exclusive access has been performed and i
Alvise Rigo writes:
> As for the RAM case, also the MMIO exclusive ranges have to be protected
> by other CPU's accesses. In order to do that, we flag the accessed
> MemoryRegion to mark that an exclusive access has been performed and is
> not concluded yet.
>
> This flag will force the other CP
As for the RAM case, also the MMIO exclusive ranges have to be protected
by other CPU's accesses. In order to do that, we flag the accessed
MemoryRegion to mark that an exclusive access has been performed and is
not concluded yet.
This flag will force the other CPUs to invalidate the exclusive ran
