Pekka Enberg wrote:
Avi Kivity wrote:
Hmm, doesn't seem to work here. I still that triple fault in guest.
Can you add a printk to see what value is returned and why?
Argh, it's a off-by one bug in my userspace tool... So the CPU really
does support 0x80000008 and I'm just an idiot. :-)
So to explain this a bit more: I'm setting 0x80000000 to 0x80000008 but
failing to install an entry for 0x80000008. I don't quite understand why
kvm_find_cpuid_entry() doesn't return NULL in this case?
Pekka
--
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
