> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, March 9, 2018 10:19 PM
>
> Instead of "syncing" the live value to what mmu_cr4_features has, make
> sure vCPU-s run with the value most recently loaded into %cr4, such that
> after the next VM exit we continue to run with the intended
>>> On 09.03.18 at 15:35, wrote:
> On 09/03/18 14:18, Jan Beulich wrote:
>> Instead of "syncing" the live value to what mmu_cr4_features has, make
>> sure vCPU-s run with the value most recently loaded into %cr4, such that
>> after the next VM exit we continue to run with the intended value rather
On 09/03/18 14:18, Jan Beulich wrote:
> Instead of "syncing" the live value to what mmu_cr4_features has, make
> sure vCPU-s run with the value most recently loaded into %cr4, such that
> after the next VM exit we continue to run with the intended value rather
> than a possibly stale one.
>
> Signe
