From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM updates for 2.6.32-rc3
Date: Mon, 05 Oct 2009 12:27:28 +0200 [thread overview]
Message-ID: <4AC9CA10.5000105@redhat.com> (raw)
Linus, please find in
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.32
some KVM fixes, most notably an EPT TLB fix on vcpu migration. Also
included is glue code for ksm. While KVM will work without this code,
any shared pages will be removed from the shadow page tables and unshared
on the next guest access, resulting in much thrashing. With the new code,
the shadow ptes are simply downgraded to read-only access.
Aurelien Jarno (1):
KVM: fix LAPIC timer period overflow
Avi Kivity (1):
KVM: Prevent overflow in KVM_GET_SUPPORTED_CPUID
Christian Borntraeger (1):
KVM: s390: fix memsize >= 4G
Izik Eidus (3):
KVM: MMU: dont hold pagecount reference for mapped sptes pages
KVM: MMU: add SPTE_HOST_WRITEABLE flag to the shadow ptes
KVM: add support for change_pte mmu notifiers
Joerg Roedel (2):
KVM: SVM: Fix tsc offset adjustment when running nested
KVM: SVM: Handle tsc in svm_get_msr/svm_set_msr correctly
Marcelo Tosatti (1):
KVM: VMX: flush TLB with INVEPT on cpu migration
arch/s390/kvm/kvm-s390.h | 2 +-
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/lapic.c | 2 +-
arch/x86/kvm/mmu.c | 84
++++++++++++++++++++++++++++++--------
arch/x86/kvm/paging_tmpl.h | 18 +++++++-
arch/x86/kvm/svm.c | 25 +++++++++---
arch/x86/kvm/vmx.c | 2 +-
arch/x86/kvm/x86.c | 2 +
virt/kvm/kvm_main.c | 14 ++++++
9 files changed, 120 insertions(+), 30 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2009-10-05 10:27 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=4AC9CA10.5000105@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).