From: Tom Lendacky <thomas.lendacky@amd.com>
To: Thomas Courrege <thomas.courrege@thorondor.fr>,
ashish.kalra@amd.com, corbet@lwn.net,
herbert@gondor.apana.org.au, john.allen@amd.com, nikunj@amd.com,
pbonzini@redhat.com, seanjc@google.com
Cc: kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v6 0/1] KVM: SEV: Add KVM_SEV_SNP_HV_REPORT_REQ command
Date: Wed, 28 Jan 2026 14:34:33 -0600 [thread overview]
Message-ID: <ff28b3dc-a695-4569-a7c7-6fb0db90bb40@amd.com> (raw)
In-Reply-To: <20260128194956.314678-1-thomas.courrege@thorondor.fr>
On 1/28/26 13:49, Thomas Courrege wrote:
> Overview
> --------
> The SEV-SNP Firmware ABI allows the hypervisor to request an
> attestation report via the SEV_CMD_SNP_HV_REPORT_REQ firmware command.
The code looks good to me, but you might want to reply to your cover
letter with more of an explanation as to why this is important to
include in KVM.
Thanks,
Tom
>
> Testing
> -------
> For testing this via QEMU, please use the following tree:
> https://github.com/Th0rOnDoR/qemu
>
> Patch History
> -------------
> v5 -> v6:
> Fix typos issues in documentation
>
> v4 -> v5:
> Set variables in reverse christmas tree order
> Fix and clean the rsp_size logic
>
> v3 -> v4:
> Add newline in documentation to avoid a warning
> Add base commit
>
> v2 -> v3:
> Add padding to structure, code format
> Write back the full MSG_REPORT_RSP structure
> Remove the memzero_explicit for the report
>
> v1 -> v2:
> Renaming, code format
> Zeroes the report before returning
>
>
> Any feedback is appreciated.
>
> Thanks,
> Thomas
>
>
> Thomas Courrege (1):
> KVM: SEV: Add KVM_SEV_SNP_HV_REPORT_REQ command
>
> .../virt/kvm/x86/amd-memory-encryption.rst | 28 +++++++++
> arch/x86/include/uapi/asm/kvm.h | 9 +++
> arch/x86/kvm/svm/sev.c | 63 +++++++++++++++++++
> drivers/crypto/ccp/sev-dev.c | 1 +
> include/linux/psp-sev.h | 31 +++++++++
> 5 files changed, 132 insertions(+)
>
>
> base-commit: e89f0e9a0a007e8c3afb8ecd739c0b3255422b00
next prev parent reply other threads:[~2026-01-28 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 19:49 Thomas Courrege
2026-01-28 19:49 ` [PATCH v6 1/1] " Thomas Courrege
2026-01-28 20:35 ` Tom Lendacky
2026-01-28 20:34 ` Tom Lendacky [this message]
2026-01-29 10:35 ` [PATCH v6 0/1] " Thomas Courrege
2026-02-11 16:37 ` Thomas Courrege
2026-02-11 16:47 ` Sean Christopherson
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=ff28b3dc-a695-4569-a7c7-6fb0db90bb40@amd.com \
--to=thomas.lendacky@amd.com \
--cc=ashish.kalra@amd.com \
--cc=corbet@lwn.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=thomas.courrege@thorondor.fr \
--cc=x86@kernel.org \
/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®