diff options
| author | Glauber Costa <glommer@redhat.com> | 2010-05-11 12:17:43 -0400 |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2010-05-19 11:41:03 +0300 |
| commit | 84478c829d0f474a1d6749207c53daacc305d4e1 (patch) | |
| tree | b901fdad494f058ee43ee7946f77ab6922dc8a1b /arch/frv/kernel/head.inc | |
| parent | 0e6ac58acbcddbc9d1687214f0d43d8657cc036c (diff) | |
| download | kernel-crypto-84478c829d0f474a1d6749207c53daacc305d4e1.tar.gz kernel-crypto-84478c829d0f474a1d6749207c53daacc305d4e1.tar.xz kernel-crypto-84478c829d0f474a1d6749207c53daacc305d4e1.zip | |
KVM: x86: export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID
Right now, we were using individual KVM_CAP entities to communicate
userspace about which cpuids we support. This is suboptimal, since it
generates a delay between the feature arriving in the host, and
being available at the guest.
A much better mechanism is to list para features in KVM_GET_SUPPORTED_CPUID.
This makes userspace automatically aware of what we provide. And if we
ever add a new cpuid bit in the future, we have to do that again,
which create some complexity and delay in feature adoption.
Signed-off-by: Glauber Costa <glommer@redhat.com>
Acked-by: Zachary Amsden <zamsden@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch/frv/kernel/head.inc')
0 files changed, 0 insertions, 0 deletions