From: David Vrabel <dvrabel@cantab.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>,
Boris Ostrovsky <Boris.Ostrovsky@oracle.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [GIT PULL] xen: bug fixes for 4.1-rc2
Date: Wed, 06 May 2015 15:12:42 +0100 [thread overview]
Message-ID: <554A215A.80606@cantab.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.1b-rc2-tag
xen: bug fixes for 4.1-rc2
- - Fix blkback regression if using persistent grants.
- - Fix various event channel related suspend/resume bugs.
- - Fix AMD x86 regression with X86_BUG_SYSRET_SS_ATTRS.
- - SWIOTLB on ARM now uses frames <4 GiB (if available) so device only
capable of 32-bit DMA work.
Thanks.
David
arch/arm/include/asm/xen/page.h | 1 +
arch/arm/xen/mm.c | 15 ++++++++++++
arch/x86/include/asm/hypervisor.h | 2 +-
arch/x86/include/asm/xen/page.h | 5 ++++
arch/x86/kernel/cpu/hypervisor.c | 4 +--
arch/x86/xen/enlighten.c | 27 ++++++++++++++-------
arch/x86/xen/suspend.c | 10 ++++++++
drivers/block/xen-blkback/blkback.c | 35 +++++++++------------------
drivers/tty/hvc/hvc_xen.c | 18 +++++++++++++-
drivers/xen/events/events_2l.c | 10 ++++++++
drivers/xen/events/events_base.c | 7 +++---
drivers/xen/gntdev.c | 28 +++------------------
drivers/xen/grant-table.c | 28 +++++++++++++++++++++
drivers/xen/manage.c | 9 ++++---
drivers/xen/swiotlb-xen.c | 2 +-
drivers/xen/xen-pciback/conf_space.c | 6 ++---
drivers/xen/xen-pciback/conf_space.h | 2 +-
drivers/xen/xen-pciback/conf_space_header.c | 2 +-
drivers/xen/xenbus/xenbus_probe.c | 29 ++++++++++++++++++++++
include/xen/grant_table.h | 1 +
include/xen/xen-ops.h | 1 +
21 files changed, 168 insertions(+), 74 deletions(-)
Ben Hutchings (1):
xen-pciback: Add name prefix to global 'permissive' variable
Bob Liu (2):
xen/blkback: safely unmap purge persistent grants
xen/grant: introduce func gnttab_unmap_refs_sync()
Boris Ostrovsky (6):
xen: Suspend ticks on all CPUs during suspend
xen/events: Clear cpu_evtchn_mask before resuming
xen/xenbus: Update xenbus event channel on resume
xen/console: Update console event channel on resume
xen/events: Set irq_info->evtchn before binding the channel to CPU in __startup_pirq()
hypervisor/x86/xen: Unset X86_BUG_SYSRET_SS_ATTRS on Xen PV guests
Stefano Stabellini (1):
xen: Add __GFP_DMA flag when xen_swiotlb_init gets free pages on ARM
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJVSiFaAAoJEFxbo/MsZsTRGRoH/i2RxP6ey8jQznPCO/aEcLXf
dbrXkqT2rS6s3VHOEzna0MIXUcNVXGE2KLyZIHaBuIl9yuzOm9MROD1vvT+ShMi4
e3eH4hx9yCRza31STaSKBYTITVkYrTMq/EkDG/98KgUcNcJ9IQpLBwD8wLrz515o
+77unEjU6HX1l1nihGn8TuPfwzdweUsF/MsRbMabHgX6pFgJzeeRMIevp92YM0+Y
u5c7ICDUdDeP3RukRVHEqEZsbnGRANUt2S4Gc38QM7yWX988TkN564CiSmkhO4kb
my1GeFcTSmwOuPGuplQ/IonY6EyY17RxDP2i9atP2fRfG8Nd+JkVDVClqoghzQg=
=S1y1
-----END PGP SIGNATURE-----
reply other threads:[~2015-05-06 14:12 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=554A215A.80606@cantab.net \
--to=dvrabel@cantab.net \
--cc=Boris.Ostrovsky@oracle.com \
--cc=Xen-devel@lists.xen.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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