KVM: Handle cpuid in the kernel instead of punting to userspace

Browse source

KVM used to handle cpuid by letting userspace decide what values to
return to the guest.  We now handle cpuid completely in the kernel.  We
still let userspace decide which values the guest will see by having
userspace set up the value table beforehand (this is necessary to allow
management software to set the cpu features to the least common denominator,
so that live migration can work).

The motivation for the change is that kvm kernel code can be impacted by
cpuid features, for example the x86 emulator.

Signed-off-by: Avi Kivity <avi@qumranet.com>

...

This commit is contained in:

Avi Kivity 2007-02-28 20:46:53 +02:00

parent 46fc147788

commit 06465c5a3a

5 changed files with 95 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

5

drivers/kvm/kvm.h

View file

69

drivers/kvm/kvm_main.c

View file

4

drivers/kvm/svm.c

View file

4

drivers/kvm/vmx.c

View file

18

include/linux/kvm.h

View file