All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Connor Kuehl <ckuehl@redhat.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Jiri Slaby <jslaby@suse.cz>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v4 0/6] Qemu SEV-ES guest support
Date: Tue, 26 Jan 2021 18:18:13 +0100	[thread overview]
Message-ID: <137ad1f2-8411-c0cd-4621-611d7f5d72d2@redhat.com> (raw)
In-Reply-To: <946ac9e2-a363-6460-87a0-9575429d3b49@amd.com>

On 26/01/21 18:13, Tom Lendacky wrote:
> Also, the new version will have a prereq against another patch series that
> has not been accepted yet:
> 
>    [PATCH v2 0/2] sev: enable secret injection to a self described area in OVMF
> 
>    https://lore.kernel.org/qemu-devel/20201214154429.11023-1-jejb@linux.ibm.com/

David reviewed it today, so even if a v3 will be needed that shouldn't 
be a problem for SEV-ES itself.

Paolo


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: Brijesh Singh <brijesh.singh@amd.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Connor Kuehl <ckuehl@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Jiri Slaby <jslaby@suse.cz>, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v4 0/6] Qemu SEV-ES guest support
Date: Tue, 26 Jan 2021 18:18:13 +0100	[thread overview]
Message-ID: <137ad1f2-8411-c0cd-4621-611d7f5d72d2@redhat.com> (raw)
In-Reply-To: <946ac9e2-a363-6460-87a0-9575429d3b49@amd.com>

On 26/01/21 18:13, Tom Lendacky wrote:
> Also, the new version will have a prereq against another patch series that
> has not been accepted yet:
> 
>    [PATCH v2 0/2] sev: enable secret injection to a self described area in OVMF
> 
>    https://lore.kernel.org/qemu-devel/20201214154429.11023-1-jejb@linux.ibm.com/

David reviewed it today, so even if a v3 will be needed that shouldn't 
be a problem for SEV-ES itself.

Paolo



  reply	other threads:[~2021-01-27 13:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 19:03 [PATCH v4 0/6] Qemu SEV-ES guest support Tom Lendacky
2020-09-25 19:03 ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 1/6] sev/i386: Add initial support for SEV-ES Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 2/6] sev/i386: Require in-kernel irqchip support for SEV-ES guests Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 3/6] sev/i386: Allow AP booting under SEV-ES Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 4/6] sev/i386: Don't allow a system reset under an SEV-ES guest Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2021-01-26 16:16   ` Paolo Bonzini
2021-01-26 16:16     ` Paolo Bonzini
2021-01-26 16:24     ` Tom Lendacky
2021-01-26 16:24       ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 5/6] kvm/i386: Use a per-VM check for SMM capability Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2020-09-25 19:03 ` [PATCH v4 6/6] sev/i386: Enable an SEV-ES guest based on SEV policy Tom Lendacky
2020-09-25 19:03   ` Tom Lendacky
2020-09-25 19:08 ` [PATCH v4 0/6] Qemu SEV-ES guest support Tom Lendacky
2020-09-25 19:08   ` Tom Lendacky
2020-09-25 22:57 ` no-reply
2020-09-25 22:57   ` no-reply
2021-01-26 16:21 ` Paolo Bonzini
2021-01-26 16:21   ` Paolo Bonzini
2021-01-26 16:49   ` Tom Lendacky
2021-01-26 16:49     ` Tom Lendacky
2021-01-26 17:13     ` Tom Lendacky
2021-01-26 17:13       ` Tom Lendacky
2021-01-26 17:18       ` Paolo Bonzini [this message]
2021-01-26 17:18         ` Paolo Bonzini

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=137ad1f2-8411-c0cd-4621-611d7f5d72d2@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=brijesh.singh@amd.com \
    --cc=ckuehl@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jslaby@suse.cz \
    --cc=kvm@vger.kernel.org \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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.