From: "Pratik R. Sampat" <prsampat@amd.com>
To: <linux-crypto@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <ashish.kalra@amd.com>,
<thomas.lendacky@amd.com>, <john.allen@amd.com>,
<herbert@gondor.apana.org.au>, <bp@alien8.de>,
<michael.roth@amd.com>, <aik@amd.com>, <pbonzini@redhat.com>,
<seanjc@google.com>, <prsampat@amd.com>
Subject: [PATCH 0/1] Support for SNP_VERIFY_MITIGATION command
Date: Mon, 30 Jun 2025 15:23:18 -0500 [thread overview]
Message-ID: <20250630202319.56331-1-prsampat@amd.com> (raw)
The SNP_VERIFY_MITIGATION command can be used to query the status of
currently supported vulnerability mitigations and to initiate
mitigations within the firmware.
The command supports two subcommands - STATUS and VERIFY.
The STATUS subcommand is used to query the supported and verified
mitigation bits. The VERIFY subcommand initiates the mitigation process
within the FW for the specified vulnerability.
Information about supported mitigations is planned to be published as
part of AMD Security Bulletins/Notices.
The patch is based on kvm/next and on "crypto/ccp: Fix locking on alloc
failure handling"[1]. The latter is required as we invoke this command
within sev_ioctl(), which already holds the mutex and does not need to
do so again if it has to reclaim snp pages.
Comments and feedback appreciated!
[1]: https://lore.kernel.org/all/20250617094354.1357771-1-aik@amd.com/
Pratik R. Sampat (1):
crypto: ccp - Add the SNP_VERIFY_MITIGATION command
Documentation/virt/coco/sev-guest.rst | 13 +++++++
drivers/crypto/ccp/sev-dev.c | 55 +++++++++++++++++++++++++++
include/linux/psp-sev.h | 30 +++++++++++++++
include/uapi/linux/psp-sev.h | 34 +++++++++++++++++
4 files changed, 132 insertions(+)
base-commit: cf931c83bfc9a33f0b0a91f6fb63a685ffeeb011
--
2.49.0
next reply other threads:[~2025-06-30 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 20:23 Pratik R. Sampat [this message]
2025-06-30 20:23 ` [PATCH 1/1] crypto: ccp - Add the " Pratik R. Sampat
2025-07-08 13:57 ` Sean Christopherson
2025-07-09 15:14 ` Pratik R. Sampat
2025-07-10 22:45 ` Sean Christopherson
2025-07-16 18:25 ` Pratik R. Sampat
2025-07-18 15:33 ` Sean Christopherson
2025-07-24 16:23 ` 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=20250630202319.56331-1-prsampat@amd.com \
--to=prsampat@amd.com \
--cc=aik@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.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 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®