From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: roy.hopkins@suse.com, ashish.kalra@amd.com, bp@alien8.de,
dave.hansen@linux.intel.com, jroedel@suse.de,
kvm@vger.kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org, michael.roth@amd.com,
mingo@redhat.com, tglx@linutronix.de, thomas.lendacky@amd.com,
x86@kernel.org
Subject: Re: [RFC PATCH 0/5] Extend SEV-SNP SVSM support with a kvm_vcpu per VMPL
Date: Wed, 23 Oct 2024 10:33:21 -0400 [thread overview]
Message-ID: <526445c102e47fbc1179a76a85661c89581c29e5.camel@HansenPartnership.com> (raw)
In-Reply-To: <8db215c5-4393-4db1-883c-431fed9dfd59@redhat.com>
On Wed, 2024-10-23 at 13:48 +0200, Paolo Bonzini wrote:
> On 10/21/24 21:51, Sean Christopherson wrote:
> > On Fri, Oct 18, 2024, James Bottomley wrote:
> > > > I've prepared this series as an extension to the RFC patch
> > > > series: 'SEV-SNP support for running an SVSM' posted by Tom
> > > > Lendacky [1]. This extends the support for transitioning a vCPU
> > > > between VM Privilege Levels (VMPLs) by storing the vCPU state
> > > > for each VMPL in its own `struct kvm_vcpu`. This additionally
> > > > allows for separate APICs for each VMPL.
> > >
> > > I couldn't attend KVM forum, but I understand based on feedback
> > > at a session there, Paolo took the lead to provide an
> > > architecture document for this feature, is that correct?
> >
> > Yep.
> >
> > > Just asking because I haven't noticed anything about this on the
> > > list.
> >
> > Heh, there's quite a queue of blocked readers (and writers!) at
> > this point ;-)
>
> Well, at least one person had a writer's block instead.
>
> I had it almost ready but then noticed a few hiccups in the design we
> came up with, and have been seating on it for a while. I'm sending
> it now, finishing the commit messages.
Thanks for doing that. For those on linux-coco who don't follow the
KVM list, the document is here:
https://lore.kernel.org/kvm/20241023124507.280382-6-pbonzini@redhat.com/
Regards,
James
prev parent reply other threads:[~2024-10-23 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 18:17 Roy Hopkins
2024-09-16 18:17 ` [RFC PATCH 1/5] kvm: Move kvm_vcpu fields into common structure Roy Hopkins
2024-09-16 18:17 ` [RFC PATCH 2/5] x86/kvm: Create a child struct kvm_vcpu for each VMPL Roy Hopkins
2024-09-16 18:17 ` [RFC PATCH 3/5] kvm/sev: Update SEV VMPL handling to use multiple struct kvm_vcpus Roy Hopkins
2024-09-16 18:17 ` [RFC PATCH 4/5] x86/kvm: Add x86 field to find the default VMPL that IRQs should target Roy Hopkins
2024-09-16 18:17 ` [RFC PATCH 5/5] x86/kvm: Add target VMPL to IRQs and send to APIC for VMPL Roy Hopkins
2024-10-18 15:36 ` [RFC PATCH 0/5] Extend SEV-SNP SVSM support with a kvm_vcpu per VMPL James Bottomley
2024-10-21 19:51 ` Sean Christopherson
2024-10-23 11:48 ` Paolo Bonzini
2024-10-23 14:33 ` James Bottomley [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=526445c102e47fbc1179a76a85661c89581c29e5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=roy.hopkins@suse.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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 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®