From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: [GIT PULL] KVM updates for 3.3-rc2
Date: Sun, 05 Feb 2012 12:36:32 +0200 [thread overview]
Message-ID: <4F2E5BB0.7040702@redhat.com> (raw)
Linus, please pull from:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.3
Fixing a regression with the PMU MSRs when PMU virtualization is
disabled, a guest-internal DoS with the SYSCALL instruction, and a dirty
memory logging race that may cause live migration to fail.
Gleb Natapov (1):
KVM: do not #GP on perf MSR writes when vPMU is disabled
Stephan Bärwolf (2):
KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid"
KVM: x86: fix missing checks in syscall emulation
Takuya Yoshikawa (1):
KVM: Fix __set_bit() race in mark_page_dirty() during dirty logging
arch/x86/include/asm/kvm_emulate.h | 16 +++++++++++
arch/x86/kvm/emulate.c | 51
++++++++++++++++++++++++++++++++++++
arch/x86/kvm/x86.c | 45 +++++++++++++++++++++++++++++++
virt/kvm/kvm_main.c | 2 +-
4 files changed, 113 insertions(+), 1 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2012-02-05 10:36 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=4F2E5BB0.7040702@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