| commit | dadf3011c85d5cb165e3cc4434df187ed3d294dd | |
| author | Sunil Muthuswamy <sunilmut@microsoft.com> | |
| Thu, 27 Feb 2020 21:01:04 +0000 (27 21:01 +0000) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Mon, 16 Mar 2020 22:02:22 +0000 (16 23:02 +0100) | ||
| tree | 67054aaee2a8937c1f0011b987c076850ae2634f | treesnapshot (tar.gz zip) |
| parent | 6785e767017a3fcc39e245b7bca2c383b8bf39ef | commitdiff |
WHPX: Use QEMU values for trapped CPUID
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 (i.e. after the partition has
been setup). That is needed to be able to set the CPUID values in
the hypervisor during VCPU init.
Until that support comes, use the QEMU values for the trapped CPUIDs.
Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
Message-Id: <SN4PR2101MB0880A8323EAD0CD0E8E2F423C0EB0@SN4PR2101MB0880.namprd21.prod.outlook.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
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 (i.e. after the partition has
been setup). That is needed to be able to set the CPUID values in
the hypervisor during VCPU init.
Until that support comes, use the QEMU values for the trapped CPUIDs.
Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
Message-Id: <SN4PR2101MB0880A8323EAD0CD0E8E2F423C0EB0@SN4PR2101MB0880.namprd21.prod.outlook.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| target/i386/whpx-all.c | diffblobblamehistory |