From: Sean Christopherson <seanjc@google.com>
To: Michael Roth <michael.roth@amd.com>
Cc: kvm@vger.kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
jroedel@suse.de, thomas.lendacky@amd.com,
liam.merwick@oracle.com, huibo.wang@amd.com,
Dionna Glaze <dionnaglaze@google.com>
Subject: Re: [PATCH v7 1/2] KVM: Introduce KVM_EXIT_SNP_REQ_CERTS for SNP certificate-fetching
Date: Fri, 23 Jan 2026 09:17:45 -0800 [thread overview]
Message-ID: <aXOtOVrr2SpnGDEg@google.com> (raw)
In-Reply-To: <20260109231732.1160759-2-michael.roth@amd.com>
On Fri, Jan 09, 2026, Michael Roth wrote:
> +KVM_EXIT_SNP_REQ_CERTS indicates an SEV-SNP guest with certificate-fetching
> +enabled (see KVM_SEV_SNP_ENABLE_REQ_CERTS) has generated an Extended Guest
> +Request NAE #VMGEXIT (SNP_GUEST_REQUEST) with message type MSG_REPORT_REQ,
> +i.e. has requested an attestation report from firmware, and would like the
> +certificate data corresponding the attestation report signature to be
^
|
to
I'll fixup when applying. Thanks for the *fantastic* documentation!
next prev parent reply other threads:[~2026-01-23 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 23:17 [PATCH v7 0/2] SEV-SNP: Add KVM support for SNP certificate fetching Michael Roth
2026-01-09 23:17 ` [PATCH v7 1/2] KVM: Introduce KVM_EXIT_SNP_REQ_CERTS for SNP certificate-fetching Michael Roth
2026-01-23 17:17 ` Sean Christopherson [this message]
2026-01-09 23:17 ` [PATCH v7 2/2] KVM: SEV: Add KVM_SEV_SNP_ENABLE_REQ_CERTS command Michael Roth
2026-01-13 12:23 ` [PATCH v7 0/2] SEV-SNP: Add KVM support for SNP certificate fetching Liam Merwick
2026-02-04 0:10 ` 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=aXOtOVrr2SpnGDEg@google.com \
--to=seanjc@google.com \
--cc=dionnaglaze@google.com \
--cc=huibo.wang@amd.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=liam.merwick@oracle.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.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.