From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Nathan Tempelman <natet@google.com>,
thomas.lendacky@amd.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, srutherford@google.com,
rientjes@google.com, brijesh.singh@amd.com, Ashish.Kalra@amd.com,
Nathaniel McCallum <npmccallum@redhat.com>,
Marc Orr <marcorr@google.com>,
"Hyunwook (Wooky) Baek" <baekhw@google.com>
Subject: Re: [RFC] KVM: x86: Support KVM VMs sharing SEV context
Date: Thu, 25 Feb 2021 12:26:49 +0100 [thread overview]
Message-ID: <d01c686b-45e0-836a-e144-4330c46f4d42@redhat.com> (raw)
In-Reply-To: <YDaFtRUAZ+P6Nrpy@google.com>
On 24/02/21 17:58, Sean Christopherson wrote:
> That being said, is there a strong need to get this into 5.12? AIUI, this hasn't
> had any meaningful testing, selftests/kvm-unit-tests or otherwise. Pushing out
> to 5.13 might give us a good chance of getting some real testing before merging,
> depending on the readiness of SEV testing support.
Note that I don't mean including this in the merge window. However, I
know that there are multiple people working on alternative SEV live
migration support, and as long as we are sure that the API is simple and
useful, it should be okay to merge this for rc2 or rc3.
Paolo
next prev parent reply other threads:[~2021-02-25 11:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 8:59 [RFC] KVM: x86: Support KVM VMs sharing SEV context Nathan Tempelman
2021-02-24 9:18 ` Paolo Bonzini
2021-02-24 16:58 ` Sean Christopherson
2021-02-25 11:26 ` Paolo Bonzini [this message]
2021-02-24 17:37 ` Sean Christopherson
2021-02-25 3:55 ` Steve Rutherford
2021-03-12 23:47 ` Nathan Tempelman
2021-03-16 17:52 ` Sean Christopherson
2021-03-16 17:58 ` Paolo Bonzini
2021-03-16 18:08 ` Sean Christopherson
2021-02-25 3:44 ` Steve Rutherford
2021-02-25 14:57 ` Tom Lendacky
2021-02-25 18:49 ` Steve Rutherford
2021-03-05 22:36 ` Ashish Kalra
2021-03-09 17:45 ` Sean Christopherson
2021-02-25 17:53 ` James Bottomley
2021-02-25 18:18 ` Ashish Kalra
2021-02-25 20:33 ` Paolo Bonzini
2021-02-26 13:30 ` Ashish Kalra
2021-02-25 20:36 ` Paolo Bonzini
2021-03-05 14:04 ` Ashish Kalra
2021-03-05 15:13 ` Paolo Bonzini
2021-03-05 20:43 ` Nathan Tempelman
2021-03-11 15:30 ` Tobin Feldman-Fitzthum
2021-03-11 16:29 ` Paolo Bonzini
2021-03-15 17:05 ` Tobin Feldman-Fitzthum
2021-03-15 17:29 ` Paolo Bonzini
2021-05-24 21:29 ` Kalra, Ashish
2021-05-24 21:29 ` Kalra, Ashish
2021-05-27 15:51 ` Kalra, Ashish
2021-05-27 15:51 ` Kalra, Ashish
2021-06-01 8:26 ` Kalra, Ashish
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=d01c686b-45e0-836a-e144-4330c46f4d42@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ashish.Kalra@amd.com \
--cc=baekhw@google.com \
--cc=brijesh.singh@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcorr@google.com \
--cc=natet@google.com \
--cc=npmccallum@redhat.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--cc=srutherford@google.com \
--cc=thomas.lendacky@amd.com \
--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 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.