summaryrefslogtreecommitdiffstats
path: root/virt/kvm/Kconfig
diff options
context:
space:
mode:
authorBorislav Petkov <bp@suse.de>2013-10-29 12:54:56 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2013-10-30 18:54:41 +0100
commit84cffe499b9418d6c3b4de2ad9599cc2ec50c607 (patch)
treee6558ea19648dd028cd877640d9fa8a934c42dee /virt/kvm/Kconfig
parent0bc5eedb82a54ccd9cbf79825226dd068427a94a (diff)
downloadop-kernel-dev-84cffe499b9418d6c3b4de2ad9599cc2ec50c607.zip
op-kernel-dev-84cffe499b9418d6c3b4de2ad9599cc2ec50c607.tar.gz
kvm: Emulate MOVBE
This basically came from the need to be able to boot 32-bit Atom SMP guests on an AMD host, i.e. a host which doesn't support MOVBE. As a matter of fact, qemu has since recently received MOVBE support but we cannot share that with kvm emulation and thus we have to do this in the host. We're waay faster in kvm anyway. :-) So, we piggyback on the #UD path and emulate the MOVBE functionality. With it, an 8-core SMP guest boots in under 6 seconds. Also, requesting MOVBE emulation needs to happen explicitly to work, i.e. qemu -cpu n270,+movbe... Just FYI, a fairly straight-forward boot of a MOVBE-enabled 3.9-rc6+ kernel in kvm executes MOVBE ~60K times. Signed-off-by: Andre Przywara <andre@andrep.de> Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud