All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikunj A Dadhania <nikunj@amd.com>
To: <seanjc@google.com>, <pbonzini@redhat.com>, <kvm@vger.kernel.org>
Cc: <thomas.lendacky@amd.com>, <santosh.shukla@amd.com>, <nikunj@amd.com>
Subject: [PATCH v3 0/2] KVM: SEV: Improve GHCB Version Handling for SEV-ES/SEV-SNP
Date: Mon, 4 Aug 2025 14:39:43 +0530	[thread overview]
Message-ID: <20250804090945.267199-1-nikunj@amd.com> (raw)

As discussed here[1]:

Refactor SEV's GHCB version handling to improve clarity and ABI stability.
* Set the default GHCB version (2) for SEV-ES guests earlier in the flow
* Remove the GHCB_VERSION_DEFAULT macro in favor of hardcoded values to
  prevent potential ABI issues
* Improve comments to better explain version requirements.
* Enforce minimum GHCB version for SEV-SNP guests.

Patches are based on kvm/next

1. https://lore.kernel.org/kvm/aHp9EGExmlq9Kx9T@google.com/

Nikunj A Dadhania (2):
  KVM: SEV: Drop GHCB_VERSION_DEFAULT and open code it
  KVM: SEV: Enforce minimum GHCB version requirement for SEV-SNP guests

 arch/x86/kvm/svm/sev.c | 25 ++++++++++++++-----------
 1 file changed, 14 insertions(+), 11 deletions(-)


base-commit: 196d9e72c4b0bd68b74a4ec7f52d248f37d0f030
-- 
2.43.0


             reply	other threads:[~2025-08-04  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04  9:09 Nikunj A Dadhania [this message]
2025-08-04  9:09 ` [PATCH v3 1/2] KVM: SEV: Drop GHCB_VERSION_DEFAULT and open code it Nikunj A Dadhania
2025-08-04  9:09 ` [PATCH v3 2/2] KVM: SEV: Enforce minimum GHCB version requirement for SEV-SNP guests Nikunj A Dadhania
2025-08-19 18:28   ` Sean Christopherson
2025-08-20  5:29     ` Nikunj A. Dadhania

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=20250804090945.267199-1-nikunj@amd.com \
    --to=nikunj@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=santosh.shukla@amd.com \
    --cc=seanjc@google.com \
    --cc=thomas.lendacky@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.