diff options
author | 2009-08-10 17:07:24 -0500 | |
---|---|---|
committer | 2009-08-24 08:02:55 -0500 | |
commit | 4a1418e07bdcfaa3177739e04707ecaec75d89e1 (patch) | |
tree | a68b7017b184850330000afa416d4ed419bb736a /qemu-monitor.hx | |
parent | Add a configure switch to enable / disable all user targets. I felt compelled... (diff) | |
download | qemu-kvm-4a1418e07bdcfaa3177739e04707ecaec75d89e1.tar.gz qemu-kvm-4a1418e07bdcfaa3177739e04707ecaec75d89e1.tar.bz2 qemu-kvm-4a1418e07bdcfaa3177739e04707ecaec75d89e1.zip |
Unbreak large mem support by removing kqemu
kqemu introduces a number of restrictions on the i386 target. The worst is that
it prevents large memory from working in the default build.
Furthermore, kqemu is fundamentally flawed in a number of ways. It relies on
the TSC as a time source which will not be reliable on a multiple processor
system in userspace. Since most modern processors are multicore, this severely
limits the utility of kqemu.
kvm is a viable alternative for people looking to accelerate qemu and has the
benefit of being supported by the upstream Linux kernel. If someone can
implement work arounds to remove the restrictions introduced by kqemu, I'm
happy to avoid and/or revert this patch.
N.B. kqemu will still function in the 0.11 series but this patch removes it from
the 0.12 series.
Paul, please Ack or Nack this patch.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'qemu-monitor.hx')
-rw-r--r-- | qemu-monitor.hx | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/qemu-monitor.hx b/qemu-monitor.hx index 11bdb2c2d..f56354bc6 100644 --- a/qemu-monitor.hx +++ b/qemu-monitor.hx @@ -57,8 +57,6 @@ show virtual to physical memory mappings (i386 only) show the active virtual memory mappings (i386 only) @item info hpet show state of HPET (i386 only) -@item info kqemu -show KQEMU information @item info kvm show KVM information @item info usb |