From: David Vrabel <dvrabel@cantab.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <Boris.Ostrovsky@oracle.com>
Subject: [GIT PULL] xen: regression and bug fixes for 4.0-rc1
Date: Tue, 24 Feb 2015 11:37:19 +0000 [thread overview]
Message-ID: <54EC626F.6060609@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 stable/for-linus-4.0-rc1-tag
xen: regression and bug fixes for 4.0-rc1
- - Fix two regression introduced in 4.0-rc1 affecting PV/PVH guests in
certain configurations.
- - Prevent pvscsi frontends bypassing backend checks.
- - Allow privcmd hypercalls to be preempted even on kernel with
voluntary preemption. This fixes soft-lockups with long running
toolstack hypercalls (e.g., when creating/destroying large domains).
Thanks.
David
arch/x86/kernel/entry_32.S | 3 +++
arch/x86/kernel/entry_64.S | 3 +++
arch/x86/xen/enlighten.c | 20 +++++++++++++++++++-
drivers/xen/Makefile | 2 +-
drivers/xen/preempt.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
drivers/xen/privcmd.c | 2 ++
drivers/xen/xen-scsiback.c | 14 ++++++--------
include/xen/xen-ops.h | 26 ++++++++++++++++++++++++++
8 files changed, 104 insertions(+), 10 deletions(-)
Boris Ostrovsky (2):
x86/xen: Make sure X2APIC_ENABLE bit of MSR_IA32_APICBASE is not set
x86/xen: Initialize cr4 shadow for 64-bit PV(H) guests
David Vrabel (1):
x86/xen: allow privcmd hypercalls to be preempted
Juergen Gross (1):
xen-scsiback: mark pvscsi frontend request consumed only after last read
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJU7GJvAAoJEFxbo/MsZsTRseEH/05CvyCcM3S9m01BKY2rxj0k
j0obP0u5PD/NTAu/+E8zmzJXrZz8n+riV/8SFtnhnxnKWNjPqOXSP4jYMli0ToL8
fQY4nNjKvvqaHS/EGzbDrcT8Fwk1DeurPTAmcp4v9c/JWl+kPlTDvpXy2042mk3v
8amIcPQX0L9+6oXKtV0M3rTN9wpLkXapURlzvVJw5FQFfxpAEyMuMomnZ5yZsD6w
ZIb6ee0AZD+T4V22cV5nt2Pu3Gk/HDuK4WJgKkp3SDuFrqApjtz64Dn3T2IB2FK+
hinTbF701RnM1GNGCwwUU6nveKN46FeX+pWy2g++r6E2Mkxg7+1nsrXjHRE/b50=
=T1XY
-----END PGP SIGNATURE-----
reply other threads:[~2015-02-24 11:37 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=54EC626F.6060609@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=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