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] [thread-next>] [day] [month] [year] [list]
Message-ID: <6028e1a0fad729f28451782754417b0be3aea7ed.camel@HansenPartnership.com>
Date: Fri, 18 Oct 2024 11:36:32 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: roy.hopkins@...e.com
Cc: 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, 
	pbonzini@...hat.com, seanjc@...gle.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

> 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?  Just asking because I haven't
noticed anything about this on the list.

Regards,

James


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ