From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [GIT PULL] (xen) stable/bug.fixes for 3.1-rc6
Date: Fri, 16 Sep 2011 09:48:46 -0400 [thread overview]
Message-ID: <20110916134846.GA27234@phenom.oracle.com> (raw)
Hey Linus,
Please git pull the following branch:
git pull git://oss.oracle.com/git/kwilk/xen.git stable/bug.fixes
which has fixes in:
1). The E820 setup code (which we are planning to cleanup in 3.2/3.3 time
-frame as it is getting bigger and nastier).
2). Taking a spinlock while later calling the generic IRQ code which
uses a mutex - causing the "BUG: you took spinlock while sleeping."
Fortunately the fix is quite simple - s/spin/mutex/.
3). The Linux guest when it runs under HVM tries to enable as many PV
things as it can. One of them is the spinlocks - but sadly we are
doing it too late and end up with baremetal ticket spinlocks and
PV byte locks running at the same time. Hilarity ensues with the guest
locking up.. we will revisit this in 3.3 time-frame.
4). Lastly, we fix up the check for overflow and also add a WARN
just in case it happens.
They aren't as spectacular as the previous git pull I sent that
had a bug since 2.6.27.. but nonetheless please pull!
David Vrabel (1):
xen/e820: if there is no dom0_mem=, don't tweak extra_pages.
Jan Beulich (1):
xen/i386: follow-up to "replace order-based range checking of M2P table by linear one"
Konrad Rzeszutek Wilk (1):
xen/irq: Alter the locking to use a mutex instead of a spinlock.
Stefano Stabellini (1):
xen: disable PV spinlocks on HVM
arch/x86/xen/mmu.c | 6 ++----
arch/x86/xen/setup.c | 10 ++++++----
arch/x86/xen/smp.c | 1 -
drivers/xen/events.c | 40 ++++++++++++++++++++--------------------
4 files changed, 28 insertions(+), 29 deletions(-)
reply other threads:[~2011-09-16 13:49 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=20110916134846.GA27234@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.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
all inboxes | Powered by JetHome®