From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.39
Date: Thu, 26 May 2011 22:16:09 +0200 [thread overview]
Message-ID: <4DDEB509.2060801@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
After silently releasing kvm-kmod-2.6.38.6 last week as a stable update,
here comes the next major new version:
http://sourceforge.net/projects/kvm/files/kvm-kmod/2.6.39/kvm-kmod-2.6.39.tar.bz2/download
The list of changes looks rather unspectacular, also due to the fact
that not all new features can be made available via kmod, e.g. directed
yield for guest spinlock optimizations.
Major KVM changes since kvm-kmod-2.6.38.6:
- more micro-optimization of vmentry/exit path
- VMX: various small fixes related to real mode
- SVM: Add support for perf-kvm
- further soft-MMU improvements and fixes
- restore PREEMPT-RT compatibility (allows to update KVM in
2.6.33.x-rt)
kvm-kmod changes:
- fix for crashes on XSAVE-capable hosts
- account for Fedora kernels with backported vzalloc
- remove obsolete IA64 arch
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
reply other threads:[~2011-05-26 20:16 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=4DDEB509.2060801@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).