On 04/11/2010 01:02 PM, Pekka Enberg wrote:
It should work without 80000008 set up - failure should happen only if it is setup incorrectly:int cpuid_maxphyaddr(struct kvm_vcpu *vcpu) { struct kvm_cpuid_entry2 *best; best = kvm_find_cpuid_entry(vcpu, 0x80000008, 0); if (best) return best->eax & 0xff; return 36; }Well, like I said, if I don't add an entry for it in struct kvm_cpuid2 that's passed to KVM_SET_CPUID2 ioctl, I see a triple fault on Core 2 Duo CPU that doesn't seem to have native 0x80000008.
Do you have a function 8, though? Looks like a bug in kvm may confuse the two.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
