public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	KVM list <kvm@vger.kernel.org>
Subject: [GIT PULL] KVM fixes for 2.6.34-rc5
Date: Wed, 21 Apr 2010 13:59:52 +0300	[thread overview]
Message-ID: <4BCEDAA8.5000608@redhat.com> (raw)

Linus, please pull a bunch of kvm fixes from

   git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.34

Shortlog/diffstat follow.

Andre Przywara (1):
       KVM: allow bit 10 to be cleared in MSR_IA32_MC4_CTL

Avi Kivity (2):
       KVM: Don't spam kernel log when injecting exceptions due to bad 
cr writes
       KVM: VMX: Save/restore rflags.vm correctly in real mode

Gleb Natapov (1):
       KVM: take srcu lock before call to complete_pio()

Jan Kiszka (1):
       KVM: x86: Fix TSS size check for 16-bit tasks

Lai Jiangshan (1):
       KVM: Add missing srcu_read_lock() for kvm_mmu_notifier_release()

Sridhar Samudrala (1):
       KVM: Increase NR_IOBUS_DEVS limit to 200

Takuya Yoshikawa (2):
       KVM: SVM: Fix memory leaks that happen when svm_create_vcpu() fails
       KVM: fix the handling of dirty bitmaps to avoid overflows

Xiao Guangrong (1):
       KVM: MMU: fix kvm_mmu_zap_page() and its calling path

  arch/ia64/kvm/kvm-ia64.c  |    9 ++++---
  arch/powerpc/kvm/book3s.c |    5 ++-
  arch/x86/kvm/mmu.c        |   11 ++++++---
  arch/x86/kvm/svm.c        |   25 ++++++++++++++---------
  arch/x86/kvm/vmx.c        |   24 ++++++++++++++--------
  arch/x86/kvm/x86.c        |   48 
+++++++++++++++------------------------------
  include/linux/kvm_host.h  |    7 +++++-
  virt/kvm/kvm_main.c       |   17 +++++++++++----
  8 files changed, 79 insertions(+), 67 deletions(-)

-- 
error compiling committee.c: too many arguments to function


                 reply	other threads:[~2010-04-21 11:00 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=4BCEDAA8.5000608@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