From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>
Subject: [GIT PULL] KVM fixes for 3.5-rc3
Date: Sun, 24 Jun 2012 19:17:06 +0300 [thread overview]
Message-ID: <4FE73D82.4040004@redhat.com> (raw)
Linus,
Please pull a couple of kvm fixes from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
Fixing a scheduling-while-atomic bug in the ppc code, and a bug which allowed
pci bridges to be assigned to guests.
----------------------------------------------------------------
Jan Kiszka (1):
KVM: Fix PCI header check on device assignment
Paul Mackerras (1):
KVM: PPC: Book3S HV: Drop locks around call to kvmppc_pin_guest_page
arch/powerpc/kvm/book3s_hv.c | 96 ++++++++++++++++++++++++++++++--------------
virt/kvm/assigned-dev.c | 4 +-
2 files changed, 67 insertions(+), 33 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2012-06-24 16:17 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=4FE73D82.4040004@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 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).