KVM: Fix MAXPHYADDR calculation when cpuid does not support it
authorAvi Kivity <avi@redhat.com>
Sun, 11 Apr 2010 12:33:32 +0000 (15:33 +0300)
committerAvi Kivity <avi@redhat.com>
Mon, 17 May 2010 09:17:36 +0000 (12:17 +0300)
commitf7a711971edd952352a89698db1d36f469e25f77
tree69e0ea723f0a408c634af5dea10dcccdfe4aef35
parente46479f852adab6027e4950d69400d967bf7bc6f
KVM: Fix MAXPHYADDR calculation when cpuid does not support it

MAXPHYADDR is derived from cpuid 0x80000008, but when that isn't present, we
get some random value.

Fix by checking first that cpuid 0x80000008 is supported.

Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
arch/x86/kvm/x86.c