From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-linus-3.7-rc5-tag
Date: Fri, 9 Nov 2012 09:11:27 -0500 [thread overview]
Message-ID: <20121109141127.GA16019@phenom.dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.7-rc5-tag
which has bug-fixes. There are three ARM compile fixes (we forgot to export
certain functions and if the drivers are built as an module - we go belly-up).
There is also an mismatch of irq_enter() / exit_idle() calls sequence - which were
fixed some time ago in other piece of codes, but failed to appear in the Xen code.
Lastly a fix for to help in the field with troubleshooting in case we cannot get
the appropriate parameter and also fallback code when working with very old hypervisors.
Please pull!
arch/arm/xen/enlighten.c | 11 +++++
arch/x86/include/asm/xen/hypercall.h | 21 +++------
drivers/xen/Makefile | 1 +
drivers/xen/events.c | 2 +-
drivers/xen/fallback.c | 80 ++++++++++++++++++++++++++++++++++
include/xen/hvm.h | 34 +++++++++++++-
6 files changed, 132 insertions(+), 17 deletions(-)
Jan Beulich (1):
xen/hypercall: fix hypercall fallback code for very old hypervisors
Konrad Rzeszutek Wilk (3):
xen/hvm: If we fail to fetch an HVM parameter print out which flag it is.
xen/generic: Disable fallback build on ARM.
xen/arm: Fix compile errors when drivers are compiled as modules.
Mojiong Qiu (1):
xen/events: fix RCU warning, or Call idle notifier after irq_enter()
Stefano Stabellini (1):
xen/arm: Fix compile errors when drivers are compiled as modules (export more).
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2012-11-09 14:11 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=20121109141127.GA16019@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/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).