All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pratik R. Sampat" <prsampat@amd.com>
To: <qemu-devel@nongnu.org>
Cc: <kvm@vger.kernel.org>, <michael.roth@amd.com>,
	<thomas.lendacky@amd.com>, <ashish.kalra@amd.com>,
	<pbonzini@redhat.com>, <prsampat@amd.com>
Subject: [PATCH 0/2] i386/sev: Enhanced SMT Protection for SEV-SNP guests
Date: Mon, 14 Sep 2026 16:22:42 +0000	[thread overview]
Message-ID: <cover.1789399242.git.prsampat@amd.com> (raw)

Enhanced SMT Protection (ESMTP) is an SEV-SNP feature that lets a guest
constrain what runs on the sibling thread of the core its vCPUs execute
on. Each vCPU's VMSA carries a VCPU_ID and a VCPU_SIBLING_MASK, and
hardware admits a VMRUN only when the sibling thread is idle in host
mode or is running a vCPU that the mask permits.

This series adds support for to opt-in esmtp support from KVM and
engages core scheduling onto the vCPUs to bundle trusted siblings in one
group.

Usage
-----
Requires patched Linux and edk2 builds. Launch an SEV-SNP guest with
ESMTP enabled on the sev-snp-guest object:

  -object sev-snp-guest,id=sev0,cbitpos=51,reduced-phys-bits=1,esmtp=on

ESMTP is opt-in because it carries a performance cost as VMRUN stalls
until the sibling runs work from a trusted vCPU or is in idle.

The guest reports the feature in dmesg among the SNP feature names:

  # dmesg | grep -i SEV

Pratik R. Sampat (2):
  i386/sev: Introduce Enhanced SMT Protection for SEV-SNP
  i386/sev: Add core scheduling for ESMTP enabled guests

 qapi/qom.json     |  9 ++++++-
 target/i386/sev.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++
 target/i386/sev.h |  1 +
 3 files changed, 71 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2026-09-14 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 16:22 Pratik R. Sampat [this message]
2026-09-14 16:22 ` [PATCH 1/2] i386/sev: Introduce Enhanced SMT Protection for SEV-SNP Pratik R. Sampat
2026-09-14 16:22 ` [PATCH 2/2] i386/sev: Add core scheduling for ESMTP enabled guests Pratik R. Sampat

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=cover.1789399242.git.prsampat@amd.com \
    --to=prsampat@amd.com \
    --cc=ashish.kalra@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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.