From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [ANNOUNCE] kvm-kmod-3.1
Date: Tue, 25 Oct 2011 13:03:24 +0200 [thread overview]
Message-ID: <4EA6977C.5010600@siemens.com> (raw)
This is the kvm-kmod compat wrapper release based on KVM modules of
Linux 3.1 (see [1] for background information). The package is available
for download from
http://sourceforge.net/projects/kvm/files/kvm-kmod/3.1/kvm-kmod-3.1.tar.bz2/download
KVM changes since kvm-kmod-3.0b:
- initial version of VMX nesting
- steal time support (inform guest about the time it was scheduled out)
- faster MMIO
- additional CPU features exposed to the guest, most importantly SMEP
kvm-kmod changes:
- fix for cross-building kvm-kmod
- Drop unused PROCESSOR variable from config.mak
As kernel.org is still out of reach for me, I'm hosting the kvm-kmod git
tree now on my server:
git://git.kiszka.org/kvm-kmod.git
http://git.kiszka.org/kvm-kmod.git
This will likely remain the primary repository because it's also not
suffering from the excessively long mirroring latencies kernel.org had
to cope with. Those latencies made buildbot runs that require public git
access really unhandy.
Jan
[1] http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules
reply other threads:[~2011-10-25 11: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=4EA6977C.5010600@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).