From: "Aithal, Srikanth" <sraithal@amd.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Naveen N Rao <naveen@kernel.org>
Subject: Re: [PATCH 2/2] KVM: selftests: Verify SEV+ guests can read and write EFER, CR0, CR4, and CR8
Date: Wed, 11 Mar 2026 10:26:42 +0530 [thread overview]
Message-ID: <52031d70-b194-44bf-892d-85f667b9869e@amd.com> (raw)
In-Reply-To: <20260310211841.2552361-3-seanjc@google.com>
On 3/11/2026 2:48 AM, Sean Christopherson wrote:
> Add "do no harm" testing of EFER, CR0, CR4, and CR8 for SEV+ guests to
> verify that the guest can read and write the registers, without hitting
> e.g. a #VC on SEV-ES guests due to KVM incorrectly trying to intercept a
> register.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> .../selftests/kvm/include/x86/processor.h | 23 ++++++++++++++
> .../selftests/kvm/x86/sev_smoke_test.c | 30 +++++++++++++++++++
> 2 files changed, 53 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/include/x86/processor.h b/tools/testing/selftests/kvm/include/x86/processor.h
> index 4ebae4269e68..469a22122157 100644
> --- a/tools/testing/selftests/kvm/include/x86/processor.h
> +++ b/tools/testing/selftests/kvm/include/x86/processor.h
> @@ -557,6 +557,11 @@ static inline uint64_t get_cr0(void)
> return cr0;
> }
>
> +static inline void set_cr0(uint64_t val)
> +{
> + __asm__ __volatile__("mov %0, %%cr0" : : "r" (val) : "memory");
> +}
> +
> static inline uint64_t get_cr3(void)
> {
> uint64_t cr3;
> @@ -566,6 +571,11 @@ static inline uint64_t get_cr3(void)
> return cr3;
> }
>
> +static inline void set_cr3(uint64_t val)
> +{
> + __asm__ __volatile__("mov %0, %%cr3" : : "r" (val) : "memory");
> +}
> +
> static inline uint64_t get_cr4(void)
> {
> uint64_t cr4;
> @@ -580,6 +590,19 @@ static inline void set_cr4(uint64_t val)
> __asm__ __volatile__("mov %0, %%cr4" : : "r" (val) : "memory");
> }
>
> +static inline uint64_t get_cr8(void)
> +{
> + uint64_t cr8;
> +
> + __asm__ __volatile__("mov %%cr8, %[cr8]" : [cr8]"=r"(cr8));
> + return cr8;
> +}
> +
> +static inline void set_cr8(uint64_t val)
> +{
> + __asm__ __volatile__("mov %0, %%cr8" : : "r" (val) : "memory");
> +}
> +
> static inline void set_idt(const struct desc_ptr *idt_desc)
> {
> __asm__ __volatile__("lidt %0"::"m"(*idt_desc));
> diff --git a/tools/testing/selftests/kvm/x86/sev_smoke_test.c b/tools/testing/selftests/kvm/x86/sev_smoke_test.c
> index 86ad1c7d068f..8bd37a476f15 100644
> --- a/tools/testing/selftests/kvm/x86/sev_smoke_test.c
> +++ b/tools/testing/selftests/kvm/x86/sev_smoke_test.c
> @@ -13,6 +13,30 @@
> #include "linux/psp-sev.h"
> #include "sev.h"
>
> +static void guest_sev_test_msr(uint32_t msr)
> +{
> + uint64_t val = rdmsr(msr);
> +
> + wrmsr(msr, val);
> + GUEST_ASSERT(val == rdmsr(msr));
> +}
> +
> +#define guest_sev_test_reg(reg) \
> +do { \
> + uint64_t val = get_##reg(); \
> + \
> + set_##reg(val); \
> + GUEST_ASSERT(val == get_##reg()); \
> +} while (0)
> +
> +static void guest_sev_test_regs(void)
> +{
> + guest_sev_test_msr(MSR_EFER);
> + guest_sev_test_reg(cr0);
> + guest_sev_test_reg(cr3);
> + guest_sev_test_reg(cr4);
> + guest_sev_test_reg(cr8);
> +}
>
> #define XFEATURE_MASK_X87_AVX (XFEATURE_MASK_FP | XFEATURE_MASK_SSE | XFEATURE_MASK_YMM)
>
> @@ -24,6 +48,8 @@ static void guest_snp_code(void)
> GUEST_ASSERT(sev_msr & MSR_AMD64_SEV_ES_ENABLED);
> GUEST_ASSERT(sev_msr & MSR_AMD64_SEV_SNP_ENABLED);
>
> + guest_sev_test_regs();
> +
> wrmsr(MSR_AMD64_SEV_ES_GHCB, GHCB_MSR_TERM_REQ);
> vmgexit();
> }
> @@ -34,6 +60,8 @@ static void guest_sev_es_code(void)
> GUEST_ASSERT(rdmsr(MSR_AMD64_SEV) & MSR_AMD64_SEV_ENABLED);
> GUEST_ASSERT(rdmsr(MSR_AMD64_SEV) & MSR_AMD64_SEV_ES_ENABLED);
>
> + guest_sev_test_regs();
> +
> /*
> * TODO: Add GHCB and ucall support for SEV-ES guests. For now, simply
> * force "termination" to signal "done" via the GHCB MSR protocol.
> @@ -47,6 +75,8 @@ static void guest_sev_code(void)
> GUEST_ASSERT(this_cpu_has(X86_FEATURE_SEV));
> GUEST_ASSERT(rdmsr(MSR_AMD64_SEV) & MSR_AMD64_SEV_ENABLED);
>
> + guest_sev_test_regs();
> +
> GUEST_DONE();
> }
>
Tested this on my machine:
# selftests: kvm: sev_smoke_test
# Random seed: 0x6b8b4567
ok 81 selftests: kvm: sev_smoke_test
Tested-by: Srikanth Aithal <sraithal@amd.com>
prev parent reply other threads:[~2026-03-11 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 21:18 [PATCH 0/2] KVM: SEV: Fix a CR8 intercept goof with SEV-ES guests Sean Christopherson
2026-03-10 21:18 ` [PATCH 1/2] KVM: SEV: Don't set CR8 write intercept when disabling AVIC for " Sean Christopherson
2026-03-11 4:54 ` Aithal, Srikanth
2026-03-10 21:18 ` [PATCH 2/2] KVM: selftests: Verify SEV+ guests can read and write EFER, CR0, CR4, and CR8 Sean Christopherson
2026-03-11 4:56 ` Aithal, Srikanth [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=52031d70-b194-44bf-892d-85f667b9869e@amd.com \
--to=sraithal@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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®