From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [ANNOUNCE] kvm-kmod-3.5
Date: Thu, 02 Aug 2012 11:47:23 +0200 [thread overview]
Message-ID: <501A4CAB.1080002@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Here comes the kvm-kmod that corresponds to kernel 3.5. The package is
available from
http://sourceforge.net/projects/kvm/files/kvm-kmod/3.5/kvm-kmod-3.5.tar.bz2/download
See [1] for further details on kvm-kmod.
Major KVM changes since kvm-kmod-3.4:
- additional instruction emulation
- page-crossing MMIO
- faster dirty logging
- module autoload
- more efficient MSI injection ABI
- minor optimizations and fixes, including a buffer overflow in the
userspace API
kvm-kmod changes:
- Stop distributing kernel headers
[1] http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
reply other threads:[~2012-08-02 9:47 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=501A4CAB.1080002@web.de \
--to=jan.kiszka@web.de \
--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).