From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: [GIT PULL] KVM fixes for 2.6.30-rc7
Date: Mon, 25 May 2009 20:16:36 +0300 [thread overview]
Message-ID: <4A1AD274.6030305@redhat.com> (raw)
Linus,
The upcoming F11 release has uncovered a couple of bugs relating to the
reloading to the PDPTRs in PAE guests. While the bugs are not recent
regressions, the switch to PAE as a default kernel, coupled with the use
of the fancy priority inherited futexes in audio code, cause the bug to
start affecting people.
Futexes enter into the picture here as their initialization code
deliberately writes into the NULL pointer. If the PDPTRs have not been
correctly reloaded, this write hits the low kernel mappings, and the
write succeeds where the code expects it to fail, disabling the pi futex
subsystem.
So please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.30
To get
Avi Kivity (2):
KVM: Make paravirt tlb flush also reload the PAE PDPTRs
KVM: Fix PDPTR reloading on CR4 writes
arch/x86/kvm/mmu.c | 3 +--
arch/x86/kvm/x86.c | 6 +++++-
2 files changed, 6 insertions(+), 3 deletions(-)
--
error compiling committee.c: too many arguments to function
reply other threads:[~2009-05-25 17:16 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=4A1AD274.6030305@redhat.com \
--to=avi@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