On 8/10/21 1:05 AM, Gerd Hoffmann wrote:
> Hi,
>
>>> I still really don't understand the need for the CPUID loop. KVM only ever
>>> programs CPUID function 0x4000, right?
>
> Nope. When you enable hyper-v emulation features you'll go find the kvm
> cpuid @ 0x4000 and the hyper-v cpuid
Hi,
> > I still really don't understand the need for the CPUID loop. KVM only ever
> > programs CPUID function 0x4000, right?
Nope. When you enable hyper-v emulation features you'll go find the kvm
cpuid @ 0x4000 and the hyper-v cpuid @ 0x4100 (or the other way
around, not sure).
Hello Tom,
On Mon, Aug 09, 2021 at 08:41:27AM -0500, Tom Lendacky wrote:
> On 8/2/21 7:31 AM, Ashish Kalra wrote:
> > +
> > + Signature[12] = '\0';
> > + for (mKvmLeaf = 0x4000; mKvmLeaf < 0x4001; mKvmLeaf += 0x100) {
>
> I still really don't understand the need for the CPUID loop. KVM
On 8/2/21 7:31 AM, Ashish Kalra wrote:
> From: Ashish Kalra
>
> Add support to check if we are running inside KVM HVM and
> KVM HVM supports SEV Live Migration feature.
>
> Cc: Jordan Justen
> Cc: Ard Biesheuvel
> Signed-off-by: Ashish Kalra
> ---
>
From: Ashish Kalra
Add support to check if we are running inside KVM HVM and
KVM HVM supports SEV Live Migration feature.
Cc: Jordan Justen
Cc: Ard Biesheuvel
Signed-off-by: Ashish Kalra
---
OvmfPkg/Include/Library/MemEncryptSevLib.h| 27
++
