From: Paolo Bonzini <pbonzini@redhat.com>
To: Sunil Muthuswamy <sunilmut@microsoft.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] WHPX: Use QEMU values for trapped CPUID
Date: Fri, 28 Feb 2020 11:59:48 +0100 [thread overview]
Message-ID: <da8ebdd7-26e8-ee3d-39f6-5744e49abcc7@redhat.com> (raw)
In-Reply-To: <SN4PR2101MB0880A8323EAD0CD0E8E2F423C0EB0@SN4PR2101MB0880.namprd21.prod.outlook.com>
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 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>
> ---
> target/i386/whpx-all.c | 42 ++++++++++++++++++------------------------
> 1 file changed, 18 insertions(+), 24 deletions(-)
>
> diff --git a/target/i386/whpx-all.c b/target/i386/whpx-all.c
> index 35601b8176..4fe5a78b29 100644
> --- a/target/i386/whpx-all.c
> +++ b/target/i386/whpx-all.c
> @@ -980,38 +980,32 @@ static int whpx_vcpu_run(CPUState *cpu)
> WHV_REGISTER_VALUE reg_values[5];
> WHV_REGISTER_NAME reg_names[5];
> UINT32 reg_count = 5;
> - UINT64 rip, rax, rcx, rdx, rbx;
> + UINT64 cpuid_fn, rip = 0, rax = 0, rcx = 0, rdx = 0, rbx = 0;
> + X86CPU *x86_cpu = X86_CPU(cpu);
> + CPUX86State *env = &x86_cpu->env;
>
> memset(reg_values, 0, sizeof(reg_values));
>
> rip = vcpu->exit_ctx.VpContext.Rip +
> vcpu->exit_ctx.VpContext.InstructionLength;
> - switch (vcpu->exit_ctx.CpuidAccess.Rax) {
> - case 1:
> - rax = vcpu->exit_ctx.CpuidAccess.DefaultResultRax;
> - /* Advertise that we are running on a hypervisor */
> - rcx =
> - vcpu->exit_ctx.CpuidAccess.DefaultResultRcx |
> - CPUID_EXT_HYPERVISOR;
> -
> - rdx = vcpu->exit_ctx.CpuidAccess.DefaultResultRdx;
> - rbx = vcpu->exit_ctx.CpuidAccess.DefaultResultRbx;
> - break;
> + cpuid_fn = vcpu->exit_ctx.CpuidAccess.Rax;
> +
> + /*
> + * Ideally, these should be supplied to the hypervisor during VCPU
> + * initialization and it should be able to satisfy this request.
> + * But, currently, WHPX doesn't support setting CPUID values in the
> + * hypervisor once the partition has been setup, which is too late
> + * since VCPUs are realized later. For now, use the values from
> + * QEMU to satisfy these requests, until WHPX adds support for
> + * being able to set these values in the hypervisor at runtime.
> + */
> + cpu_x86_cpuid(env, cpuid_fn, 0, (UINT32 *)&rax, (UINT32 *)&rbx,
> + (UINT32 *)&rcx, (UINT32 *)&rdx);
> + switch (cpuid_fn) {
> case 0x80000001:
> - rax = vcpu->exit_ctx.CpuidAccess.DefaultResultRax;
> /* Remove any support of OSVW */
> - rcx =
> - vcpu->exit_ctx.CpuidAccess.DefaultResultRcx &
> - ~CPUID_EXT3_OSVW;
> -
> - rdx = vcpu->exit_ctx.CpuidAccess.DefaultResultRdx;
> - rbx = vcpu->exit_ctx.CpuidAccess.DefaultResultRbx;
> + rcx &= ~CPUID_EXT3_OSVW;
> break;
> - default:
> - rax = vcpu->exit_ctx.CpuidAccess.DefaultResultRax;
> - rcx = vcpu->exit_ctx.CpuidAccess.DefaultResultRcx;
> - rdx = vcpu->exit_ctx.CpuidAccess.DefaultResultRdx;
> - rbx = vcpu->exit_ctx.CpuidAccess.DefaultResultRbx;
> }
>
> reg_names[0] = WHvX64RegisterRip;
>
Queued if you need that, thanks.
Paolo
prev parent reply other threads:[~2020-02-28 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 21:01 [PATCH] WHPX: Use QEMU values for trapped CPUID Sunil Muthuswamy
2020-02-27 21:09 ` Eduardo Habkost
2020-02-27 21:29 ` [EXTERNAL] " Sunil Muthuswamy
2020-02-28 10:59 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da8ebdd7-26e8-ee3d-39f6-5744e49abcc7@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sunilmut@microsoft.com \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).