From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"paul@xen.org" <paul@xen.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yosry@kernel.org" <yosry@kernel.org>
Subject: Re: [PATCH 07/11] KVM: x86: Add mode-aware versions of kvm_<reg>_{read,write}() helpers
Date: Tue, 14 Apr 2026 08:26:47 +0000 [thread overview]
Message-ID: <04265eaad625a7e594f1f1b273cfde3c90b84934.camel@intel.com> (raw)
In-Reply-To: <20260409235622.2052730-8-seanjc@google.com>
> --- a/arch/x86/kvm/svm/nested.c
> +++ b/arch/x86/kvm/svm/nested.c
> @@ -757,7 +757,7 @@ static void nested_vmcb02_prepare_save(struct vcpu_svm *svm)
>
> svm->vcpu.arch.cr2 = save->cr2;
>
> - kvm_rax_write(vcpu, save->rax);
> + kvm_rax_write_raw(vcpu, save->rax);
> kvm_rsp_write(vcpu, save->rsp);
> kvm_rip_write(vcpu, save->rip);
>
> @@ -1238,7 +1238,7 @@ static int nested_svm_vmexit_update_vmcb12(struct kvm_vcpu *vcpu)
> vmcb12->save.rflags = kvm_get_rflags(vcpu);
> vmcb12->save.rip = kvm_rip_read(vcpu);
> vmcb12->save.rsp = kvm_rsp_read(vcpu);
> - vmcb12->save.rax = kvm_rax_read(vcpu);
> + vmcb12->save.rax = kvm_rax_read_raw(vcpu);
Not sure whether it matters, I think there's an inconsistency here:
The "rax" one has "raw" postfix, but "rsp" doesn't, despite in practice it
is also a "raw" operation. Ditto for "rip", although it will be moved out
of the "regs[]" GPR array.
But maybe they are different?
[...]
> case EXIT_REASON_MSR_WRITE:
> - kvm_rcx_write(vcpu, tdx->vp_enter_args.r12);
> - kvm_rax_write(vcpu, tdx->vp_enter_args.r13 & -1u);
> - kvm_rdx_write(vcpu, tdx->vp_enter_args.r13 >> 32);
> + kvm_ecx_write(vcpu, tdx->vp_enter_args.r12);
> + kvm_eax_write(vcpu, tdx->vp_enter_args.r13 & -1u);
Nit: the "& -1u" isn't needed anymore with using kvm_eax_write(), but maybe
we should just focus on replacing the functions in this patch but leave
cleanup in the future.
[...]
> @@ -12184,23 +12185,23 @@ static void __set_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs)
> vcpu->arch.emulate_regs_need_sync_from_vcpu = true;
> vcpu->arch.emulate_regs_need_sync_to_vcpu = false;
>
> - kvm_rax_write(vcpu, regs->rax);
> - kvm_rbx_write(vcpu, regs->rbx);
> - kvm_rcx_write(vcpu, regs->rcx);
> - kvm_rdx_write(vcpu, regs->rdx);
> - kvm_rsi_write(vcpu, regs->rsi);
> - kvm_rdi_write(vcpu, regs->rdi);
> + kvm_rax_write_raw(vcpu, regs->rax);
> + kvm_rbx_write_raw(vcpu, regs->rbx);
> + kvm_rcx_write_raw(vcpu, regs->rcx);
> + kvm_rdx_write_raw(vcpu, regs->rdx);
> + kvm_rsi_write_raw(vcpu, regs->rsi);
> + kvm_rdi_write_raw(vcpu, regs->rdi);
> kvm_rsp_write(vcpu, regs->rsp);
> - kvm_rbp_write(vcpu, regs->rbp);
> + kvm_rbp_write_raw(vcpu, regs->rbp);
>
Ditto, the "rsp" one stands out. :-)
[...]
> +static __always_inline void kvm_e##lname##_write(struct kvm_vcpu *vcpu, u32 val) \
It seems tab is used before the 'u32 val'. Seems no need.
next prev parent reply other threads:[~2026-04-14 8:26 UTC|newest]
Thread overview: 33+ 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-21 23:26 ` Yosry Ahmed
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
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-21 23:27 ` Yosry Ahmed
2026-04-09 23:56 ` [PATCH 06/11] KVM: x86: Move kvm_<reg>_{read,write}() definitions to x86.h Sean Christopherson
2026-04-21 23:32 ` Yosry Ahmed
2026-04-22 0:40 ` Sean Christopherson
2026-04-22 20:03 ` Yosry Ahmed
2026-04-23 19:17 ` 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 [this message]
2026-04-14 15:42 ` Sean Christopherson
2026-04-14 22:40 ` Huang, Kai
2026-04-14 9:02 ` Binbin Wu
2026-04-23 22:12 ` Sean Christopherson
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-21 23:19 ` Yosry Ahmed
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=04265eaad625a7e594f1f1b273cfde3c90b84934.camel@intel.com \
--to=kai.huang@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=seanjc@google.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
all inboxes | Powered by JetHome®