From: Sean Christopherson <seanjc@google.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Paul Durrant <paul@xen.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yosry Ahmed <yosry@kernel.org>
Subject: Re: [PATCH 03/11] KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest
Date: Wed, 15 Apr 2026 14:29:30 -0700 [thread overview]
Message-ID: <aeADOo9f-wW4opEH@google.com> (raw)
In-Reply-To: <38309411-b86c-43cc-8451-cfdf43d84302@linux.intel.com>
On Mon, Apr 13, 2026, Binbin Wu wrote:
>
>
> On 4/10/2026 7:56 AM, Sean Christopherson wrote:
> > Don't truncate RAX when handling a Xen hypercall for a guest with protected
> > state,
>
> It sounds like KVM supports Xen hypercalls from a guest with protected state
"supports" is a strong word. It's theoretically possible. I highly doubt anyone
has evern actually tried to smush the two together.
> normally, but it seems that a warning would still be triggered by
> kvm_rax_read() for checking whether it's a Hyper-V hypercall even after the
> whole patch set when the userspace enables KVM_XEN_HVM_CONFIG_INTERCEPT_HCALL
> for the guest.
Ooh, fun.
> > as KVM's ABI is to assume the guest is in 64-bit for such cases
> > (the guest leaving garbage in 63:32 after a transition to 32-bit mode is
> > far less likely than 63:32 being necessary to complete the hypercall).
> >
> > Fixes: b5aead0064f3 ("KVM: x86: Assume a 64-bit hypercall for guests with protected state")
> > Signed-off-by: Sean Christopherson <seanjc@google.com>
> > ---
> > arch/x86/kvm/xen.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
> > index 6d9be74bb673..895095dc684e 100644
> > --- a/arch/x86/kvm/xen.c
> > +++ b/arch/x86/kvm/xen.c
> > @@ -1678,15 +1678,14 @@ int kvm_xen_hypercall(struct kvm_vcpu *vcpu)
> > bool handled = false;
> > u8 cpl;
> >
> > - input = (u64)kvm_register_read(vcpu, VCPU_REGS_RAX);
> > -
> > /* Hyper-V hypercalls get bit 31 set in EAX */
> > - if ((input & 0x80000000) &&
> > + if ((kvm_rax_read(vcpu) & 0x80000000) &&
>
> Should this function call be replaced with kvm_rax_read_raw() in patch 7/11
> if KVM allows the Xen hypercalls from a guest with protected state to avoid
> triggering the warning?
Yeah, that does seem like the correct behavior.
> > kvm_hv_hypercall_enabled(vcpu))
> > return kvm_hv_hypercall(vcpu);
> >
> > longmode = is_64_bit_hypercall(vcpu);
> > if (!longmode) {
> > + input = (u32)kvm_rax_read(vcpu);
> > params[0] = (u32)kvm_rbx_read(vcpu);
> > params[1] = (u32)kvm_rcx_read(vcpu);
> > params[2] = (u32)kvm_rdx_read(vcpu);
> > @@ -1696,6 +1695,7 @@ int kvm_xen_hypercall(struct kvm_vcpu *vcpu)
> > }
> > else {
> > #ifdef CONFIG_X86_64
> > + input = (u64)kvm_rax_read(vcpu);
> > params[0] = (u64)kvm_rdi_read(vcpu);
> > params[1] = (u64)kvm_rsi_read(vcpu);
> > params[2] = (u64)kvm_rdx_read(vcpu);
>
next prev parent reply other threads:[~2026-04-15 21:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 23:56 [PATCH 00/11] KVM: x86: Clean up kvm_<reg>_{read,write}() mess Sean Christopherson
2026-04-09 23:56 ` [PATCH 01/11] KVM: SVM: Truncate INVLPGA address in compatibility mode Sean Christopherson
2026-04-09 23:56 ` [PATCH 02/11] KVM: x86/xen: Bug the VM if 32-bit KVM observes a 64-bit mode hypercall Sean Christopherson
2026-04-09 23:56 ` [PATCH 03/11] KVM: x86/xen: Don't truncate RAX when handling hypercall from protected guest Sean Christopherson
2026-04-13 10:36 ` Binbin Wu
2026-04-15 21:29 ` Sean Christopherson [this message]
2026-04-09 23:56 ` [PATCH 04/11] KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode Sean Christopherson
2026-04-13 12:19 ` Huang, Kai
2026-04-15 21:37 ` Sean Christopherson
2026-04-15 23:32 ` Huang, Kai
2026-04-16 0:27 ` Sean Christopherson
2026-04-16 1:40 ` Huang, Kai
2026-04-09 23:56 ` [PATCH 05/11] KVM: x86: Trace hypercall register *after* truncating values for 32-bit Sean Christopherson
2026-04-09 23:56 ` [PATCH 06/11] KVM: x86: Move kvm_<reg>_{read,write}() definitions to x86.h Sean Christopherson
2026-04-09 23:56 ` [PATCH 07/11] KVM: x86: Add mode-aware versions of kvm_<reg>_{read,write}() helpers Sean Christopherson
2026-04-14 8:26 ` Huang, Kai
2026-04-14 15:42 ` Sean Christopherson
2026-04-14 22:40 ` Huang, Kai
2026-04-14 9:02 ` Binbin Wu
2026-04-09 23:56 ` [PATCH 08/11] KVM: x86: Drop non-raw kvm_<reg>_write() helpers Sean Christopherson
2026-04-09 23:56 ` [PATCH 09/11] KVM: nSVM: Use kvm_rax_read() now that it's mode-aware Sean Christopherson
2026-04-09 23:56 ` [PATCH 10/11] Revert "KVM: VMX: Read 32-bit GPR values for ENCLS instructions outside of 64-bit mode" Sean Christopherson
2026-04-16 1:42 ` Huang, Kai
2026-04-09 23:56 ` [PATCH 11/11] KVM: x86: Harden is_64_bit_hypercall() against bugs on 32-bit kernels Sean Christopherson
2026-04-16 1:43 ` Huang, Kai
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=aeADOo9f-wW4opEH@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=yosry@kernel.org \
/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