From: Marcelo Tosatti <mtosatti@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: [GIT PULL] KVM fixes for 3.8-rc2
Date: Tue, 8 Jan 2013 16:05:27 -0200 [thread overview]
Message-ID: <20130108180527.GA24962@amt.cnet> (raw)
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
To receive the following KVM bug fixes
Alexander Graf (1):
Merge commit 'origin/master' into kvm-ppc-3.8
Andreas Schwab (1):
KVM: PPC: Book3S HV: Fix compilation without CONFIG_PPC_POWERNV
Bharat Bhushan (1):
powerpc: Corrected include header path in kvm_para.h
Gleb Natapov (1):
Merge branch 'kvm-ppc-3.8' of https://github.com/agraf/linux-2.6 into master
Li Zhong (1):
Add rcu user eqs exception hooks for async page fault
Marcelo Tosatti (1):
KVM: x86: use dynamic percpu allocations for shared msrs area
arch/powerpc/include/uapi/asm/kvm_para.h | 2 +-
arch/powerpc/kvm/book3s_hv_ras.c | 4 ++++
arch/x86/kernel/kvm.c | 12 ++++++++++--
arch/x86/kvm/x86.c | 24 ++++++++++++++++++------
4 files changed, 33 insertions(+), 9 deletions(-)
reply other threads:[~2013-01-08 18:05 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=20130108180527.GA24962@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@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