On 20/01/2023 2:39 pm, Andrew Cooper wrote:
> On 20/01/2023 2:20 pm, Jan Beulich wrote:
>> On 20.01.2023 15:10, Andrew Cooper wrote:
>>> On 20/01/2023 1:10 pm, Jan Beulich wrote:
On 20.01.2023 12:45, Andrew Cooper wrote:
> This is a global variable (actually 3, one per GUEST_PAGING_LEVEL),
On 20/01/2023 2:20 pm, Jan Beulich wrote:
> On 20.01.2023 15:10, Andrew Cooper wrote:
>> On 20/01/2023 1:10 pm, Jan Beulich wrote:
>>> On 20.01.2023 12:45, Andrew Cooper wrote:
This is a global variable (actually 3, one per GUEST_PAGING_LEVEL),
operated
on using atomics only (with n
On 20.01.2023 15:10, Andrew Cooper wrote:
> On 20/01/2023 1:10 pm, Jan Beulich wrote:
>> On 20.01.2023 12:45, Andrew Cooper wrote:
>>> This is a global variable (actually 3, one per GUEST_PAGING_LEVEL), operated
>>> on using atomics only (with no regard to what else shares the same
>>> cacheline),
On 20/01/2023 1:10 pm, Jan Beulich wrote:
> On 20.01.2023 12:45, Andrew Cooper wrote:
>> This is a global variable (actually 3, one per GUEST_PAGING_LEVEL), operated
>> on using atomics only (with no regard to what else shares the same
>> cacheline),
>> which emits a diagnostic (in debug builds on
On 20.01.2023 12:45, Andrew Cooper wrote:
> This is a global variable (actually 3, one per GUEST_PAGING_LEVEL), operated
> on using atomics only (with no regard to what else shares the same cacheline),
> which emits a diagnostic (in debug builds only) without changing any program
> behaviour.
>
>
This is a global variable (actually 3, one per GUEST_PAGING_LEVEL), operated
on using atomics only (with no regard to what else shares the same cacheline),
which emits a diagnostic (in debug builds only) without changing any program
behaviour.
Based on read-only p2m types including logdirty, this
