From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH RESEND v2 0/7] x86/alternatives: Support for automatic padding calculations
Date: Mon, 26 Feb 2018 11:34:57 +0000 [thread overview]
Message-ID: <1519644904-11349-1-git-send-email-andrew.cooper3@citrix.com> (raw)
[ Resend properly numbered this time. ]
This is the end result of a lot of work I started during the Spectre/Meltdown
embargo window, and deferred because it was taking too long. It finally
resolves the explict padding calculations for the SPEC_CTRL alternatives.
This series depends on Roger's "x86/clang: allow integrated assembler usage"
and has been tested with a mainline version of clang.
http://xenbits.xen.org/gitweb/?p=people/andrewcoop/xen.git;a=shortlog;h=refs/heads/alternatives-v2
Andrew Cooper (7):
x86/alt: Drop unused alternative infrastructure
x86/alt: Clean up struct alt_instr and its users
x86/alt: Clean up the assembly used to generate alternatives
x86/asm: Remove opencoded uses of altinstruction_entry
x86/alt: Support for automatic padding calculations
x86/alt: Drop explicit padding of origin sites
x86/build: Use new .nop directive when available
xen/arch/x86/Rules.mk | 8 ++
xen/arch/x86/alternative.c | 48 ++++++++---
xen/arch/x86/x86_64/compat/entry.S | 26 +++---
xen/arch/x86/x86_64/entry.S | 20 +----
xen/include/asm-x86/alternative-asm.h | 113 +++++++++++++++++++-------
xen/include/asm-x86/alternative.h | 148 +++++++++++++++++++---------------
xen/include/asm-x86/asm_defns.h | 32 +++-----
xen/include/asm-x86/nops.h | 7 --
xen/include/asm-x86/spec_ctrl_asm.h | 19 ++---
9 files changed, 244 insertions(+), 177 deletions(-)
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-02-26 11:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 11:34 Andrew Cooper [this message]
2018-02-26 11:34 ` [PATCH v2 1/7] x86/alt: Drop unused alternative infrastructure Andrew Cooper
2018-02-26 11:34 ` [PATCH v2 2/7] x86/alt: Clean up struct alt_instr and its users Andrew Cooper
2018-02-26 11:35 ` [PATCH v2 3/7] x86/alt: Clean up the assembly used to generate alternatives Andrew Cooper
2018-02-26 14:09 ` Roger Pau Monné
2018-02-28 15:59 ` Jan Beulich
2018-03-01 12:44 ` Wei Liu
2018-02-26 11:35 ` [PATCH v2 4/7] x86/asm: Remove opencoded uses of altinstruction_entry Andrew Cooper
2018-02-26 11:35 ` [PATCH v2 5/7] x86/alt: Support for automatic padding calculations Andrew Cooper
2018-02-28 16:16 ` Jan Beulich
2018-02-28 17:26 ` Andrew Cooper
2018-03-01 7:26 ` Jan Beulich
2018-02-26 11:35 ` [PATCH v2 6/7] x86/alt: Drop explicit padding of origin sites Andrew Cooper
2018-02-26 11:35 ` [PATCH v2 7/7] x86/build: Use new .nop directive when available Andrew Cooper
2018-02-26 12:31 ` Roger Pau Monné
2018-02-26 13:08 ` Andrew Cooper
2018-02-26 14:27 ` Roger Pau Monné
2018-02-28 16:22 ` Jan Beulich
2018-02-28 17:45 ` Andrew Cooper
2018-03-01 7:28 ` Jan Beulich
2018-03-01 10:36 ` Roger Pau Monné
2018-03-01 10:54 ` Jan Beulich
2018-03-01 16:58 ` Andrew Cooper
2018-03-02 7:10 ` Jan Beulich
2018-03-02 19:34 ` Andrew Cooper
2018-03-05 8:33 ` 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=1519644904-11349-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.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).