xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: [V5 PATCH 1/1] x86/xen: Set EFER.NX and EFER.SCE in PVH guests
Date: Fri, 26 Sep 2014 18:26:38 +0100	[thread overview]
Message-ID: <5425A1CE.7090704@citrix.com> (raw)
In-Reply-To: <1410392166-16388-2-git-send-email-mukesh.rathor@oracle.com>

On 11/09/14 00:36, Mukesh Rathor wrote:
> This fixes two bugs in PVH guests:
> 
>   - Not setting EFER.NX means the NX bit in page table entries is
>     ignored on Intel processors and causes reserved bit page faults on
>     AMD processors.
> 
>   - After the Xen commit 7645640d6ff1 ("x86/PVH: don't set EFER_SCE for
>     pvh guest") PVH guests are required to set EFER.SCE to enable the
>     SYSCALL instruction.
> 
> Secondary VCPUs are started with pagetables with the NX bit set so
> EFER.NX must be set before using any stack or data segment.
> xen_pvh_cpu_early_init() is the new secondary VCPU entry point that
> sets EFER before jumping to cpu_bringup_and_idle().

Applied to devel/for-linus-3.18

Thanks.

David

      parent reply	other threads:[~2014-09-26 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1410392166-16388-1-git-send-email-mukesh.rathor@oracle.com>
2014-09-10 23:36 ` [V5 PATCH 1/1] x86/xen: Set EFER.NX and EFER.SCE in PVH guests Mukesh Rathor
     [not found] ` <1410392166-16388-2-git-send-email-mukesh.rathor@oracle.com>
2014-09-12 20:42   ` Konrad Rzeszutek Wilk
     [not found]   ` <20140912204258.GA24846@laptop.dumpdata.com>
2014-09-12 20:46     ` Mukesh Rathor
2014-09-15 14:45     ` David Vrabel
     [not found]     ` <5416FBA1.2060902@citrix.com>
2014-09-15 19:28       ` Konrad Rzeszutek Wilk
2014-09-16  1:33     ` Mukesh Rathor
2014-09-26 17:26   ` David Vrabel [this message]

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=5425A1CE.7090704@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;
as well as URLs for NNTP newsgroup(s).