From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.34
Date: Mon, 17 May 2010 12:25:01 +0200 [thread overview]
Message-ID: <4BF1197D.80101@siemens.com> (raw)
Linux 2.6.34 is out, and here comes the corresponding kvm-kmod package.
Download is available at
http://downloads.sourceforge.net/project/kvm/kvm-kmod/2.6.34/kvm-kmod-2.6.34.tar.bz2
KVM changes since kvm-kmod-2.6.34-rc3:
- VMX: blocked-by-sti must not defer NMI injections
- x86: Call vcpu_load and vcpu_put in cpuid_update
- SVM: Fix wrong intercept masks on 32 bit
- convert ioapic lock to spinlock
- x86: Fix TSS size check for 16-bit tasks
- Add missing srcu_read_lock() for kvm_mmu_notifier_release()
- Increase NR_IOBUS_DEVS limit to 200
- fix the handling of dirty bitmaps to avoid overflows
- MMU: fix kvm_mmu_zap_page() and its calling path
- VMX: Save/restore rflags.vm correctly in real mode
- allow bit 10 to be cleared in MSR_IA32_MC4_CTL
- Don't spam kernel log when injecting exceptions due to bad cr writes
- SVM: Fix memory leaks that happen when svm_create_vcpu() fails
- take srcu lock before call to complete_pio()
kvm-kmod changes:
- stop distributing generated kvm-kmod-config.h
As previously announced, this release also marks the end-of-life for the
kvm-kmod-2.6.33.x series.
reply other threads:[~2010-05-17 10:25 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=4BF1197D.80101@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 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).