[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8db215c5-4393-4db1-883c-431fed9dfd59@redhat.com>
Date: Wed, 23 Oct 2024 13:48:57 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>,
James Bottomley <James.Bottomley@...senpartnership.com>
Cc: roy.hopkins@...e.com, ashish.kalra@....com, bp@...en8.de,
dave.hansen@...ux.intel.com, jroedel@...e.de, kvm@...r.kernel.org,
linux-coco@...ts.linux.dev, linux-kernel@...r.kernel.org,
michael.roth@....com, mingo@...hat.com, tglx@...utronix.de,
thomas.lendacky@....com, x86@...nel.org
Subject: Re: [RFC PATCH 0/5] Extend SEV-SNP SVSM support with a kvm_vcpu per
VMPL
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.
Paolo
Powered by blists - more mailing lists