From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [ANNOUNCE] kvm-53 release
Date: Tue, 20 Nov 2007 11:03:28 +0200 [thread overview]
Message-ID: <4742A2E0.7000007@qumranet.com> (raw)
Most notable is that an fpu leak on AMD has been plugged. Currently
this has some performance impact; next release should restore
performance while maintaining correctness.
Changes from kvm-52:
- testsuite: exit on end of test
- batch mode for kvm_stat script
- compile fixes (Carlo Marcelo Arenas Belon, Joe Perches)
- portability (Jerone Young, Zhang Xiantao)
- disable lazy fpu on AMD (Amit Shah)
- should fix instability on AMD
- will cause performance regression, fix in progress
- x86 emulator: fix 'push r/m' emulation (Amit Shah)
- register use reduction in vmx guest entry
- infrastructure for per-vm stats
- extends existing per-vcpu stats
- add mmu, state switch, emulation statistics
- use copy_{to,from}_user to access guest memory (Izik Eidus)
- simplify access to guest page tables (Izik Eidus)
- fix entry to real mode with segment bases beyond 1MB (Jan Kiszka)
- finally kill last use of cr2 in emulator (Sheng Yang)
Notes:
If you use the modules bundled with kvm-53, you can use any version
of Linux from 2.6.9 upwards.
If you use the modules bundled with Linux 2.6.20, you need to use
kvm-12.
If you use the modules bundled with Linux 2.6.21, you need to use
kvm-17.
Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22. Some features may only be available in newer releases.
For best performance, use Linux 2.6.23-rc2 or later as the host.
http://kvm.qumranet.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
reply other threads:[~2007-11-20 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4742A2E0.7000007@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox