public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	xen-devel@lists.xenproject.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: [Xen-devel] [PATCH] x86/xen: Initialize cr4 shadow for 64-bit PV(H) guests
Date: Tue, 03 Mar 2015 09:27:34 -0500	[thread overview]
Message-ID: <54F5C4D6.9010907@oracle.com> (raw)
In-Reply-To: <CAB=NE6V6K-OceG8Vw6Zhh6JuCCxNN=R5AWHjjduv-s6qQnB5MQ@mail.gmail.com>

On 03/03/2015 12:35 AM, Luis R. Rodriguez wrote:
> On Mon, Feb 23, 2015 at 9:09 AM, David Vrabel <david.vrabel@citrix.com> wrote:
>> On 23/02/15 16:01, Boris Ostrovsky wrote:
>>> Commit 1e02ce4cccdc ("x86: Store a per-cpu shadow copy of CR4")
>>> introduced CR4 shadows.
>>>
>>> These shadows are initialized in early boot code. The commit missed
>>> initialization for 64-bit PV(H) guests that this patch adds.
>> Applied to stable/for-linus-4.0, thanks.
>>
>> Boris, can you kick of a set of tests on this branch, please?
> Do we know worst case what should blow up without this commit ?

PVH guest will crash.

-boris


  reply	other threads:[~2015-03-03 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 16:01 [PATCH] x86/xen: Initialize cr4 shadow for 64-bit PV(H) guests Boris Ostrovsky
2015-02-23 16:09 ` Andy Lutomirski
2015-02-23 16:16   ` Boris Ostrovsky
2015-02-23 17:09 ` [Xen-devel] " David Vrabel
2015-03-03  5:35   ` Luis R. Rodriguez
2015-03-03 14:27     ` Boris Ostrovsky [this message]
2015-03-03 18:15       ` Luis R. Rodriguez
2015-03-03 18:27         ` Konrad Rzeszutek Wilk

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=54F5C4D6.9010907@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mcgrof@suse.com \
    --cc=xen-devel@lists.xenproject.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