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-rc2-tag for v3.7-rc2
Date: Tue, 23 Oct 2012 12:27:07 -0400 [thread overview]
Message-ID: <20121023162707.GA16634@phenom.dumpdata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2714 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-rc2-tag
which has bug-fixes. Most of them are just code cleanup to make x86 and ARM code
work in unison. There is one serious bug-fix which manifested itself in some
applications mysteriously getting SIGKILL. Besides that nothing earth-shattering.
<copied from the signed tag>:
* Fix mysterious SIGSEGV or SIGKILL in applications due to corrupting
of the %eip when returning from a signal handler.
* Fix various ARM compile issues after the merge fallout.
* Continue on making more of the Xen generic code usable by ARM platform.
* Fix SR-IOV passthrough to mirror multifunction PCI devices.
* Fix various compile warnings.
* Remove hypercalls that don't exist anymore.
</copy from signed tag>
arch/arm/include/asm/xen/interface.h | 12 +++++++++---
arch/arm/include/asm/xen/page.h | 13 ++++++++++---
arch/arm/xen/grant-table.c | 2 +-
arch/x86/include/asm/xen/interface.h | 4 ++--
arch/x86/kernel/entry_32.S | 8 +++++---
arch/x86/kernel/entry_64.S | 2 +-
arch/x86/xen/enlighten.c | 2 --
drivers/xen/balloon.c | 3 +--
drivers/xen/dbgp.c | 2 ++
drivers/xen/events.c | 4 ++++
drivers/xen/grant-table.c | 8 ++++----
drivers/xen/sys-hypervisor.c | 4 +++-
drivers/xen/xen-pciback/vpci.c | 14 ++++++++++----
drivers/xen/xenbus/xenbus_xs.c | 2 ++
include/xen/grant_table.h | 2 +-
include/xen/interface/grant_table.h | 2 +-
include/xen/interface/memory.h | 24 ++----------------------
17 files changed, 58 insertions(+), 50 deletions(-)
David Vrabel (1):
xen/x86: don't corrupt %eip when returning from a signal handler
Ian Campbell (11):
xen: xenbus: quirk uses x86 specific cpuid
xen: sysfs: include err.h for PTR_ERR etc
xen: sysfs: fix build warning.
xen: XENMEM_translate_gpfn_list was remove ages ago and is unused.
xen: events: pirq_check_eoi_map is X86 specific
xen: grant: use xen_pfn_t type for frame_list.
xen: balloon: don't include e820.h
xen: arm: make p2m operations NOPs
xen: balloon: use correct type for frame_list
xen: arm: comment on why 64-bit xen_pfn_t is safe even on 32 bit
xen: dbgp: Fix warning when CONFIG_PCI is not enabled.
Konrad Rzeszutek Wilk (1):
xen/xenbus: Fix compile warning.
Laszlo Ersek (1):
xen PV passthru: assign SR-IOV virtual functions to separate virtual slots
Wei Yongjun (1):
xen/x86: remove duplicated include from enlighten.c
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2012-10-23 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 16:27 Konrad Rzeszutek Wilk [this message]
2012-10-23 17:37 ` [Xen-devel] [GIT PULL] (xen) stable/for-linus-3.7-rc2-tag for v3.7-rc2 Sander Eikelenboom
2012-10-23 18:53 ` Konrad Rzeszutek Wilk
2012-10-23 19:05 ` Sander Eikelenboom
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=20121023162707.GA16634@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).