mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org,  Michael Roth <michael.roth@amd.com>
Cc: 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
Subject: Re: [PATCH v7 0/2] SEV-SNP: Add KVM support for SNP certificate fetching
Date: Tue,  3 Feb 2026 16:10:27 -0800	[thread overview]
Message-ID: <177016365652.574271.13292347664843792807.b4-ty@google.com> (raw)
In-Reply-To: <20260109231732.1160759-1-michael.roth@amd.com>

On Fri, 09 Jan 2026 17:17:31 -0600, Michael Roth wrote:
> This patchset is also available at:
> 
>   https://github.com/amdese/linux/commits/snp-certs-v7
> 
> and is based on top of kvm/next (0499add8efd7)
> 
> 
> [...]

Applied to kvm-x86 svm, thanks!

[1/2] KVM: Introduce KVM_EXIT_SNP_REQ_CERTS for SNP certificate-fetching
      https://github.com/kvm-x86/linux/commit/fa9893fadbc2
[2/2] KVM: SEV: Add KVM_SEV_SNP_ENABLE_REQ_CERTS command
      https://github.com/kvm-x86/linux/commit/20c3c4108d58

--
https://github.com/kvm-x86/linux/tree/next

      parent reply	other threads:[~2026-02-04  0:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 23:17 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
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 [this message]

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=177016365652.574271.13292347664843792807.b4-ty@google.com \
    --to=seanjc@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 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®