mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Srikanth Aithal <sraithal@amd.com>,
	Naveen N Rao <naveen@kernel.org>
Subject: [PATCH 0/2] KVM: SEV: Fix a CR8 intercept goof with SEV-ES guests
Date: Tue, 10 Mar 2026 14:18:39 -0700	[thread overview]
Message-ID: <20260310211841.2552361-1-seanjc@google.com> (raw)

Fix a recently introduced bug where KVM incorrectly enables CR8 write
interception when inhibiting AVIC for SEV-ES guests, and extend the SEV+
smoke selftest to guard against similar goofs in the future.

Sean Christopherson (2):
  KVM: SEV: Don't set CR8 write intercept when disabling AVIC for SEV-ES
    guests
  KVM: selftests: Verify SEV+ guests can read and write EFER, CR0, CR4,
    and CR8

 arch/x86/kvm/svm/avic.c                       |  3 +-
 .../selftests/kvm/include/x86/processor.h     | 23 ++++++++++++++
 .../selftests/kvm/x86/sev_smoke_test.c        | 30 +++++++++++++++++++
 3 files changed, 55 insertions(+), 1 deletion(-)


base-commit: 3271085a7f1030ba9897cab60452acd370423ff1
-- 
2.53.0.473.g4a7958ca14-goog


             reply	other threads:[~2026-03-10 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 21:18 Sean Christopherson [this message]
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

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=20260310211841.2552361-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sraithal@amd.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®