On 08/02/17 18:06, George Dunlap wrote:
> On 08/02/17 13:20, Andrew Cooper wrote:
>> On 08/02/17 13:13, Jan Beulich wrote:
>> On 07.02.17 at 19:48, wrote:
Until the IPI has completed, other processors might be running on this
nested
p2m object. clear_domain_page() does not gua
On 08/02/17 13:20, Andrew Cooper wrote:
> On 08/02/17 13:13, Jan Beulich wrote:
> On 07.02.17 at 19:48, wrote:
>>> Until the IPI has completed, other processors might be running on this
>>> nested
>>> p2m object. clear_domain_page() does not guarantee to make 8-byte atomic
>>> updates, which
On 08/02/17 13:13, Jan Beulich wrote:
On 07.02.17 at 19:48, wrote:
>> Until the IPI has completed, other processors might be running on this nested
>> p2m object. clear_domain_page() does not guarantee to make 8-byte atomic
>> updates, which means that a pagewalk on a remote processor might
>>> On 07.02.17 at 19:48, wrote:
> Until the IPI has completed, other processors might be running on this nested
> p2m object. clear_domain_page() does not guarantee to make 8-byte atomic
> updates, which means that a pagewalk on a remote processor might encounter a
> partial update.
>
> This is
At 18:48 + on 07 Feb (1486493293), Andrew Cooper wrote:
> Until the IPI has completed, other processors might be running on this nested
> p2m object. clear_domain_page() does not guarantee to make 8-byte atomic
> updates, which means that a pagewalk on a remote processor might encounter a
> pa
