From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [GIT PULL] KVM fixes for 3.2-rc7
Date: Mon, 26 Dec 2011 16:02:41 +0200 [thread overview]
Message-ID: <4EF87E81.1020708@redhat.com> (raw)
Linus, please pull from:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.2
to receive an unfortunately large bunch of fixes for Linux 3.2 KVM, some
fairly critical:
- two DoS issues in the device assignment code
- an oops in the emulated PIT code
- the regression caused by incorrect exposure of the TSC deadline timer
feature to guests
- a few powerpc build fixes
Alex Williamson (2):
KVM: Remove ability to assign a device without iommu support
KVM: Device assignment permission checks
Andreas Schwab (2):
KVM: PPC: move compute_tlbie_rb to book3s_64 common header
KVM: PPC: protect use of kvmppc_h_pr
Jan Kiszka (2):
KVM: x86: Prevent starting PIT timers in the absence of irqchip
support
KVM: Don't automatically expose the TSC deadline timer in cpuid
Michael Neuling (1):
KVM: PPC: fix kvmppc_start_thread() for CONFIG_SMP=N
Scott Wood (1):
KVM: PPC: e500: include linux/export.h
Documentation/virtual/kvm/api.txt | 16 +++++
arch/powerpc/include/asm/kvm_book3s.h | 33 -----------
arch/powerpc/include/asm/kvm_book3s_64.h | 33 +++++++++++
arch/powerpc/kvm/book3s_hv.c | 2 +-
arch/powerpc/kvm/book3s_pr.c | 2 +
arch/powerpc/kvm/e500.c | 1 +
arch/x86/kvm/i8254.c | 10 ++-
arch/x86/kvm/x86.c | 19 +++---
include/linux/kvm.h | 1 +
virt/kvm/assigned-dev.c | 93
+++++++++++++++++++++++++++---
10 files changed, 154 insertions(+), 56 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2011-12-26 14:02 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=4EF87E81.1020708@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).