[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250630202319.56331-1-prsampat@amd.com>
Date: Mon, 30 Jun 2025 15:23:18 -0500
From: "Pratik R. Sampat" <prsampat@....com>
To: <linux-crypto@...r.kernel.org>
CC: <linux-kernel@...r.kernel.org>, <ashish.kalra@....com>,
<thomas.lendacky@....com>, <john.allen@....com>,
<herbert@...dor.apana.org.au>, <bp@...en8.de>, <michael.roth@....com>,
<aik@....com>, <pbonzini@...hat.com>, <seanjc@...gle.com>, <prsampat@....com>
Subject: [PATCH 0/1] Support for SNP_VERIFY_MITIGATION command
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
Powered by blists - more mailing lists