Re: KVM_SET_MP_STATE is undocumented

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Avi,

Avi Kivity kirjoitti:
I noticed that QEMU uses KVM_SET_MP_STATE but the ioctl() is completely undocumented. I assume it has something to do with multiprocessor but I am unable to work out the details unless I take a peek at arch/x86/kvm.

Patch sent.

Two more interesting but undocumented ioctls:

 - KVM_SET_IDENTITY_MAP_ADDR
 - KVM_SET_BOOT_CPU_ID

Little background: we're debugging a KVM_EXIT_UNKNOWN problem for the "largest bug-free kernel" on Core i5 machine. I've been looking at plain QEMU sources but it seems "qemu-kvm" that the person is using does much more during initialization. Do we have a known good list of mandatory steps required to properly initialize KVM on all CPUs?

			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

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux