linux-kernel - Re: [RFC PATCH 0/5] Extend SEV-SNP SVSM support with a kvm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <526445c102e47fbc1179a76a85661c89581c29e5.camel@HansenPartnership.com>
Date: Wed, 23 Oct 2024 10:33:21 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Paolo Bonzini <pbonzini@...hat.com>, Sean Christopherson
 <seanjc@...gle.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 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