On 04/09/2010 02:55 AM, Richard Simpson wrote:
On 08/04/10 08:23, Avi Kivity wrote:
Strange. Can you hack qemu-kvm's cpuid code where it issues the ioctl
KVM_SET_CPUID2 to show what the data is? I'm not where that code is in
your version of qemu-kvm.
So, basically I go round a loop and print out the contents of each
kvm_cpuid_entry2 structure.
Results below, using Andre Przywara's handy nano-kernel. I do hope that
some of this makes some kind of sense!
qemu-kvm -kernel cpuid_mb -vnc :0
80000000 0 0 8000000a 68747541 444d4163 69746e65
80000001 0 0 623 0 1 2181abfd
80000001 edx bit 20 is NX, which is cleared. So it is qemu-kvm at fault
here.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
