From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>,
Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [V2 PATCH 1/1] PVH: set EFER.NX and EFER.SCE
Date: Wed, 03 Sep 2014 10:49:07 -0400 [thread overview]
Message-ID: <54072A63.6080704@oracle.com> (raw)
In-Reply-To: <54071E6C.4080901@citrix.com>
On 09/03/2014 09:58 AM, David Vrabel wrote:
> #endif
> diff --git a/arch/x86/xen/xen-head.S b/arch/x86/xen/xen-head.S
> index 485b695..a64b464 100644
> --- a/arch/x86/xen/xen-head.S
> +++ b/arch/x86/xen/xen-head.S
> @@ -47,6 +47,40 @@ ENTRY(startup_xen)
>
> __FINIT
>
> +#ifdef CONFIG_XEN_PVH
> +#ifdef CONFIG_X86_64
CONFIG_XEN_PVH implies CONFIG_X86_64.
-boris
next prev parent reply other threads:[~2014-09-03 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 1:19 [V2 PATCH 0/1] PVH: set EFER bits Mukesh Rathor
2014-09-03 1:19 ` [V2 PATCH 1/1] PVH: set EFER.NX and EFER.SCE Mukesh Rathor
2014-09-03 13:58 ` [Xen-devel] " David Vrabel
2014-09-03 14:49 ` Boris Ostrovsky [this message]
2014-09-03 14:53 ` Andrew Cooper
2014-09-03 20:53 ` Mukesh Rathor
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=54072A63.6080704@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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