From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] KVM fixes for 2.6.35-rc6
Date: Sun, 25 Jul 2010 15:02:28 +0300 [thread overview]
Message-ID: <4C4C27D4.1010607@redhat.com> (raw)
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.35
to get a couple of fairly critical fixes for 2.6.35-rc6. One works
around the vmalloc() performance regression, the fix for which did not
make it into 2.6.35, and the other fixes failures of the RHEL 6 beta as
a guest, which has been frequently reported.
Avi Kivity (1):
KVM: Use kmalloc() instead of vmalloc() for KVM_[GS]ET_MSR
Xiao Guangrong (1):
KVM: MMU: fix conflict access permissions in direct sp
arch/x86/kvm/paging_tmpl.h | 1 +
arch/x86/kvm/x86.c | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2010-07-25 12: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=4C4C27D4.1010607@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