On 27/02/20 22:01, Sunil Muthuswamy wrote:
> Currently, WHPX is using some default values for the trapped CPUID
> functions. These were not in sync with the QEMU values because the
> CPUID values were never set with WHPX during VCPU initialization.
> Additionally, at the moment, WHPX doesn't suppor
> -Original Message-
> From: Eduardo Habkost
> Sent: Thursday, February 27, 2020 1:10 PM
> To: Sunil Muthuswamy
> Cc: Paolo Bonzini ; Richard Henderson
> ; qemu-devel@nongnu.org; Stefan Weil
>
> Subject: [EXTERNAL] Re: [PATCH] WHPX: Use QEMU values for trapped C
On Thu, Feb 27, 2020 at 09:01:04PM +, Sunil Muthuswamy wrote:
> Currently, WHPX is using some default values for the trapped CPUID
> functions. These were not in sync with the QEMU values because the
> CPUID values were never set with WHPX during VCPU initialization.
> Additionally, at the mome
Currently, WHPX is using some default values for the trapped CPUID
functions. These were not in sync with the QEMU values because the
CPUID values were never set with WHPX during VCPU initialization.
Additionally, at the moment, WHPX doesn't support setting CPUID
values in the hypervisor at runtime
