xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: stable <stable@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.18.17 Xen regression
Date: Fri, 17 Jul 2015 14:59:52 +0100	[thread overview]
Message-ID: <1437141592.32371.335.camel@citrix.com> (raw)
In-Reply-To: <559C2E60.5080400@oracle.com>

On Tue, 2015-07-07 at 15:54 -0400, Boris Ostrovsky wrote:
> Commit 63753fac67e1 ("x86: Store a per-cpu shadow copy of CR4") in 
> 3.18.y branch introduced a regression on PVH Xen guests.
> 
> Please apply 5054daa285be ("x86/xen: Initialize cr4 shadow for 64-bit 
> PV(H) guests") from mainline to fix this. 3.18.y appears to be the only 
> affected branch.

Any news on this? Our automated tests of 3.18 are continuing to fail.

Ian.

  reply	other threads:[~2015-07-17 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 19:54 3.18.17 Xen regression Boris Ostrovsky
2015-07-17 13:59 ` Ian Campbell [this message]
2015-07-17 14:09   ` Boris Ostrovsky
2015-07-17 21:23     ` Sasha Levin

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=1437141592.32371.335.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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).