From: David Vrabel <david.vrabel@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
<boris.ostrovsky@oracle.com>, <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [V1 PATCH 1/2] PVH: set EFER.NX and EFER.SCE for boot vcpu
Date: Thu, 28 Aug 2014 15:18:26 +0100 [thread overview]
Message-ID: <53FF3A32.7000805@citrix.com> (raw)
In-Reply-To: <1409178815-2026-2-git-send-email-mukesh.rathor@oracle.com>
On 27/08/14 23:33, Mukesh Rathor wrote:
> This patch addresses three things for a pvh boot vcpu:
>
> - NX bug on intel: It was recenlty discovered that NX is not being
> honored in PVH on intel since EFER.NX is not being set. The pte.NX
> bits are ignored if EFER.NX is not set on intel.
I am unconvinced by this explanation. The Intel SDM clearly states that
the XD bit in the page table entries is reserved if EFER.NXE is clear,
and thus using a entry with XD set and EFER.NXE clear should generate a
page fault (same as AMD).
You either need to find out why Intel really worked (perhaps Xen is
setting EFER.NXE on Intel?) or you need to included an errata (or
similar) reference.
> - PVH boot hang on newer xen: Following c/s on xen
>
> c/s 7645640: x86/PVH: don't set EFER_SCE for pvh guest
As I already explained in another email, the Xen change caused a
regression and must be reverted.
David
next prev parent reply other threads:[~2014-08-28 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 22:33 [V1 PATCH 0/2] Linux PVH: set EFER bits Mukesh Rathor
2014-08-27 22:33 ` [V1 PATCH 1/2] PVH: set EFER.NX and EFER.SCE for boot vcpu Mukesh Rathor
2014-08-28 14:18 ` David Vrabel [this message]
2014-08-28 23:59 ` [Xen-devel] " Mukesh Rathor
2014-08-27 22:33 ` [V1 PATCH 2/2] PVH: set EFER.NX and EFER.SCE for secondary vcpus Mukesh Rathor
2014-08-28 14:24 ` [Xen-devel] " David Vrabel
2014-08-28 14:08 ` [Xen-devel] [V1 PATCH 0/2] Linux PVH: set EFER bits David Vrabel
2014-08-28 14:15 ` Jan Beulich
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=53FF3A32.7000805@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.rathor@oracle.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