From: Feng Wu <feng.wu@intel.com>
To: xen-devel@lists.xen.org
Cc: keir.xen@gmail.com, Feng Wu <feng.wu@intel.com>, JBeulich@suse.com
Subject: [PATCH 0/3] x86: Use alternative mechanism to define CLAC/STAC
Date: Mon, 26 May 2014 15:27:50 +0800 [thread overview]
Message-ID: <1401089273-16425-1-git-send-email-feng.wu@intel.com> (raw)
This patch set ports the basic alternative mechanism from Linux to Xen
and use it to define CLAC/STAC.
Feng Wu (3):
x86: Add definitions for NOP operation
x86: Port the basic alternative mechanism from Linux to Xen
x86: Use alternative mechanism to define CLAC/STAC
xen/arch/x86/Makefile | 1 +
xen/arch/x86/alternative.c | 223 ++++++++++++++++++++++++++++++++++++++
xen/arch/x86/setup.c | 5 +
xen/arch/x86/traps.c | 15 +++
xen/arch/x86/xen.lds.S | 22 ++++
xen/include/asm-x86/alternative.h | 77 +++++++++++++
xen/include/asm-x86/asm_defns.h | 36 +++---
xen/include/asm-x86/nops.h | 71 ++++++++++++
xen/include/asm-x86/traps.h | 2 +
9 files changed, 439 insertions(+), 13 deletions(-)
create mode 100644 xen/arch/x86/alternative.c
create mode 100644 xen/include/asm-x86/alternative.h
create mode 100644 xen/include/asm-x86/nops.h
--
1.8.3.1
next reply other threads:[~2014-05-26 7:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 7:27 Feng Wu [this message]
2014-05-26 7:27 ` [PATCH 1/3] x86: Add definitions for NOP operation Feng Wu
2014-05-26 15:04 ` Andrew Cooper
2014-05-26 7:27 ` [PATCH 2/3] x86: Port the basic alternative mechanism from Linux to Xen Feng Wu
2014-05-26 15:40 ` Andrew Cooper
2014-05-26 16:16 ` Jan Beulich
2014-05-27 6:13 ` Wu, Feng
2014-05-27 9:30 ` Jan Beulich
2014-05-27 15:35 ` Jan Beulich
2014-05-26 7:27 ` [PATCH 3/3] x86: Use alternative mechanism to define CLAC/STAC Feng Wu
2014-05-26 15:49 ` Andrew Cooper
2014-05-26 16:18 ` Jan Beulich
2014-05-26 16:22 ` Andrew Cooper
2014-05-27 6:24 ` Wu, Feng
2014-05-27 15:42 ` 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=1401089273-16425-1-git-send-email-feng.wu@intel.com \
--to=feng.wu@intel.com \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xen.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).