From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.32.7
Date: Fri, 29 Jan 2010 18:56:13 +0100 [thread overview]
Message-ID: <4B63213D.7010906@siemens.com> (raw)
Yet another stable update for kvm-kmod-2.6.32. This one comes with a
bunch of smaller KVM fixes. They are mostly targeting rare corner cases
or making the kernel interface more robust against mad user space. But
one also fixing a small memory leak per created VCPU.
On the kvm-kmod framework side, we have some some improvements for
packagers (as I had to go through this pain myself) and we now deliver
kvm_para.h, so far only interesting for bleeding-edge qemu (qemu-kvm
still comes with its own copies). Longer changelog below.
Find the new version at:
https://sourceforge.net/projects/kvm/files/kvm-kmod/2.6.32.7/kvm-kmod-2.6.32.7.tar.bz2/download
KVM changes since kvm-kmod-2.6.32.4:
- only clear irq_source_id if irqchip is present
- fix lock imbalance in kvm_*_irq_source_id()
- x86: Fix leak of free lapic date in kvm_arch_vcpu_init()
- x86: Fix probable memory leak of vcpu->arch.mce_banks
- x86: Fix host_mapping_level()
- MMU: bail out pagewalk on kvm_read_guest error
- Fix race between APIC TMR and IRR
- only allow one gsi per fd
kvm-kmod changes:
- provide kvm_para.h headers
- Report missing configure run more elegantly
- Do not rename old kernel modules during installation, rely on depmod
preferring update directory
- Use standard modules_install
- small cleanups
Jan
reply other threads:[~2010-01-29 17:56 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=4B63213D.7010906@siemens.com \
--to=jan.kiszka@siemens.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.