On 8/10/21 1:05 AM, Gerd Hoffmann wrote:
Hi,Ah, thanks. I just saw the comment above get_out_of_range_cpuid_entry() inNope. When you enable hyper-v emulation features you'll go find the kvmI still really don't understand the need for the CPUID loop. KVM only ever
arch/x86/kvm/cpuid.c where HyperV would get the 0x40000000-0x400000ff
range and KVM would then get the 0x40000100-0x400001ff range (basically
each hypervisor class gets their own 0x100 range).