From: George Dunlap <george.dunlap@citrix.com>
To: He Chen <he.chen@linux.intel.com>
Cc: Wu Feng <feng.wu@intel.com>, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Wang Yong <yong.y.wang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Nakajima Jun <jun.nakajima@intel.com>
Subject: Re: [PATCH] solve SMAP/SMEP issues with 32-bit pv guests
Date: Wed, 10 Aug 2016 11:23:31 +0100 [thread overview]
Message-ID: <CAFLBxZaNKaRBcp_jsWT_528ppaNZrC7AWS5v7ARDsNXRp9REtA@mail.gmail.com> (raw)
In-Reply-To: <1470734039-15758-1-git-send-email-he.chen@linux.intel.com>
On Tue, Aug 9, 2016 at 10:13 AM, He Chen <he.chen@linux.intel.com> wrote:
> This patch is going to solve SMAP/SMEP issues with 32-bit pv guests by
> adding new xen command line options "xen_smap" and "xen_smep".
>
> For the details, please see: https://lists.xen.org/archives/html/xen-devel/2016-06/msg03441.html
>
> I am sorry that I don't have 32-bit PV environment to test this patch,
> I would really appreciate it if someone could help verify this patch :)
>
> He Chen (1):
> xen: enable/disable SMAP/SMEP for Xen itself
>
> docs/misc/xen-command-line.markdown | 14 ++++++++++++++
> xen/arch/x86/setup.c | 12 ++++++++++--
> 2 files changed, 24 insertions(+), 2 deletions(-)
>
> --
> 1.9.1
There doesn't seem to be any actual content here.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-08-10 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 9:13 [PATCH] solve SMAP/SMEP issues with 32-bit pv guests He Chen
2016-08-09 9:13 ` [PATCH] xen: enable/disable SMAP/SMEP for Xen itself He Chen
2016-08-09 12:19 ` Jan Beulich
2016-08-10 10:23 ` George Dunlap [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=CAFLBxZaNKaRBcp_jsWT_528ppaNZrC7AWS5v7ARDsNXRp9REtA@mail.gmail.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=feng.wu@intel.com \
--cc=he.chen@linux.intel.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yong.y.wang@intel.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).