From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM updates for 2.6.35-rc2
Date: Thu, 10 Jun 2010 12:31:57 +0300 [thread overview]
Message-ID: <4C10B10D.80304@redhat.com> (raw)
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.35
to receive a bunch of KVM fixes for 2.6.35-rc2, including a workaround
for a cpu erratum that can allow a guest to crash the host.
Avi Kivity (1):
KVM: MMU: Remove user access when allowing kernel access to
gpte.w=0 page
Huang Ying (1):
KVM: Avoid killing userspace through guest SRAO MCE on unmapped pages
Jan Kiszka (1):
KVM: Fix order passed to iommu_unmap
Jean Delvare (1):
KVM: powerpc: fix init/exit annotation
Joerg Roedel (2):
KVM: SVM: Handle MCEs early in the vmexit process
KVM: SVM: Implement workaround for Erratum 383
Julia Lawall (1):
KVM: ia64: Add missing spin_unlock in kvm_arch_hardware_enable()
Marcelo Tosatti (2):
KVM: MMU: invalidate and flush on spte small->large page size change
KVM: read apic->irr with ioapic lock held
arch/ia64/kvm/kvm-ia64.c | 1 +
arch/powerpc/kvm/e500.c | 2 +-
arch/x86/include/asm/msr-index.h | 1 +
arch/x86/kvm/mmu.c | 39 ++++++++++++---
arch/x86/kvm/paging_tmpl.h | 7 +--
arch/x86/kvm/svm.c | 96
+++++++++++++++++++++++++++++++++++++-
include/linux/kvm_host.h | 1 +
include/linux/mm.h | 8 +++
mm/memory-failure.c | 30 ++++++++++++
virt/kvm/ioapic.c | 3 +-
virt/kvm/iommu.c | 2 +-
virt/kvm/kvm_main.c | 30 +++++++++++-
12 files changed, 201 insertions(+), 19 deletions(-)
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2010-06-10 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 9:31 Avi Kivity [this message]
2010-06-10 16:33 ` [GIT PULL] KVM updates for 2.6.35-rc2 Linus Torvalds
2010-06-10 17:34 ` Avi Kivity
2010-06-10 17:56 ` Linus Torvalds
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=4C10B10D.80304@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 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.