From: Feng Wu <feng.wu@intel.com>
To: xen-devel@lists.xen.org
Cc: Feng Wu <feng.wu@intel.com>,
ian.campbell@citrix.com, andrew.cooper3@citrix.com, tim@xen.org,
keir.xen@gmail.com, stefano.stabellini@citrix.com,
JBeulich@suse.com
Subject: [PATCH v2 0/5] x86: Use alternative mechanism to define CLAC/STAC
Date: Thu, 29 May 2014 13:34:24 +0800 [thread overview]
Message-ID: <1401341669-5237-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.
Version 1:
* Initial version
Version 2:
* Use STR() as the only method for performing preprocessor stringificaion.
* Set ideal_nops to k8_nops by default
* Make ideal_nops static and __initdata
* Mask the lowest bit when handling relative jump in apply_alternatives()
* Move .altinstr_replacemen and altinstructions to .init section
* Include nops.h in alternative.h
* Some code style changes
There are some changes related to ARM code in the first patch of this series,
but I don't have ARM environment to verify it. The changes in x86 side have
the same logic, and I verify it in x86 side.
Feng Wu (5):
Use STR() as the only method for performing preprocessor
stringificaion
x86: Add definitions for NOP operation
x86: Make set_nmi_callback return the old nmi callback
x86: Port the basic alternative mechanism from Linux to Xen
x86: Use alternative mechanism to define CLAC/STAC
xen/arch/arm/domain_build.c | 2 +-
xen/arch/x86/Makefile | 1 +
xen/arch/x86/alternative.c | 213 ++++++++++++++++++++++++++++++++++
xen/arch/x86/efi/boot.c | 3 +-
xen/arch/x86/setup.c | 3 +
xen/arch/x86/traps.c | 4 +-
xen/arch/x86/xen.lds.S | 15 +++
xen/include/asm-arm/arm32/processor.h | 10 +-
xen/include/asm-arm/cpregs.h | 2 -
xen/include/asm-arm/sysregs.h | 2 -
xen/include/asm-x86/alternative.h | 78 +++++++++++++
xen/include/asm-x86/asm_defns.h | 25 ++--
xen/include/asm-x86/nmi.h | 4 +-
xen/include/asm-x86/nops.h | 66 +++++++++++
xen/include/xen/stringify.h | 12 --
15 files changed, 401 insertions(+), 39 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
delete mode 100644 xen/include/xen/stringify.h
--
1.8.3.1
next reply other threads:[~2014-05-29 5:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 5:34 Feng Wu [this message]
2014-05-29 5:34 ` [PATCH v2 1/5] Use STR() as the only method for performing preprocessor stringificaion Feng Wu
2014-05-29 7:00 ` Andrew Cooper
2014-05-29 15:00 ` Jan Beulich
2014-05-29 5:34 ` [PATCH v2 2/5] x86: Add definitions for NOP operation Feng Wu
2014-05-29 8:43 ` Andrew Cooper
2014-05-29 5:34 ` [PATCH v2 3/5] x86: Make set_nmi_callback return the old nmi callback Feng Wu
2014-05-29 7:01 ` Andrew Cooper
2014-05-29 5:34 ` [PATCH v2 4/5] x86: Port the basic alternative mechanism from Linux to Xen Feng Wu
2014-05-29 8:55 ` Andrew Cooper
2014-05-29 9:28 ` Wu, Feng
2014-05-29 14:59 ` Andrew Cooper
2014-05-30 4:48 ` Wu, Feng
2014-05-30 7:07 ` Jan Beulich
2014-05-29 5:34 ` [PATCH v2 5/5] x86: Use alternative mechanism to define CLAC/STAC Feng Wu
2014-05-29 8:56 ` Andrew Cooper
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=1401341669-5237-1-git-send-email-feng.wu@intel.com \
--to=feng.wu@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=keir.xen@gmail.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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).