From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Wei Liu" <wei.liu2@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 7/7] x86/build: Use new .nop directive when available
Date: Mon, 12 Feb 2018 14:40:01 +0000 [thread overview]
Message-ID: <20180212144001.jdriny2grisgjsdx@citrix.com> (raw)
In-Reply-To: <1518434587-22827-8-git-send-email-andrew.cooper3@citrix.com>
On Mon, Feb 12, 2018 at 11:23:07AM +0000, Andrew Cooper wrote:
> Newer versions of binutils are capable of emitting an exact number bytes worth
> of optimised nops. Use this in preference to .skip when available.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-12 14:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 11:23 [PATCH 0/7] x86/alternatives: Support for automatic padding calculations Andrew Cooper
2018-02-12 11:23 ` [PATCH 1/7] x86/alt: Drop unused alternative infrastructure Andrew Cooper
2018-02-12 12:30 ` Wei Liu
2018-02-12 15:56 ` Roger Pau Monné
2018-02-12 15:58 ` Andrew Cooper
2018-02-13 14:22 ` Jan Beulich
2018-02-13 14:41 ` Andrew Cooper
2018-02-13 15:33 ` Jan Beulich
2018-02-14 10:02 ` Jan Beulich
2018-02-12 11:23 ` [PATCH 2/7] x86/alt: Clean up struct alt_instr and its users Andrew Cooper
2018-02-12 12:30 ` Wei Liu
2018-02-12 16:52 ` Roger Pau Monné
2018-02-12 17:18 ` Wei Liu
2018-02-12 17:53 ` Andrew Cooper
2018-02-13 14:26 ` Jan Beulich
2018-02-21 21:22 ` Konrad Rzeszutek Wilk
2018-02-12 11:23 ` [PATCH 3/7] x86/alt: Clean up the assembly used to generate alternatives Andrew Cooper
2018-02-12 12:30 ` Wei Liu
2018-02-12 17:26 ` Roger Pau Monné
2018-02-12 17:54 ` Andrew Cooper
2018-02-13 14:37 ` Jan Beulich
2018-02-23 14:03 ` Andrew Cooper
2018-02-23 15:12 ` Jan Beulich
2018-02-23 16:24 ` Andrew Cooper
2018-02-23 17:28 ` Jan Beulich
2018-02-12 11:23 ` [PATCH 4/7] x86/asm: Remove opencoded uses of altinstruction_entry Andrew Cooper
2018-02-12 12:30 ` Wei Liu
2018-02-12 12:34 ` Andrew Cooper
2018-02-13 9:56 ` Jan Beulich
2018-02-13 10:07 ` Andrew Cooper
2018-02-13 11:10 ` Jan Beulich
2018-02-12 12:52 ` Wei Liu
2018-02-12 17:46 ` Roger Pau Monné
2018-02-12 17:59 ` Andrew Cooper
2018-02-14 9:53 ` Jan Beulich
2018-02-12 11:23 ` [PATCH 5/7] x86/alt: Support for automatic padding calculations Andrew Cooper
2018-02-12 14:39 ` Wei Liu
2018-02-12 15:04 ` Andrew Cooper
2018-02-12 18:41 ` Roger Pau Monné
2018-02-12 18:45 ` Andrew Cooper
2018-02-12 18:09 ` Roger Pau Monné
2018-02-13 9:45 ` Roger Pau Monné
2018-02-13 10:09 ` Andrew Cooper
2018-02-13 10:26 ` Roger Pau Monné
2018-02-14 9:46 ` Jan Beulich
2018-02-12 11:23 ` [PATCH 6/7] x86/alt: Drop explicit padding of origin sites Andrew Cooper
2018-02-12 14:39 ` Wei Liu
2018-02-12 18:12 ` Roger Pau Monné
2018-02-14 9:53 ` Jan Beulich
2018-02-12 11:23 ` [PATCH 7/7] x86/build: Use new .nop directive when available Andrew Cooper
2018-02-12 14:40 ` Wei Liu [this message]
2018-02-13 11:08 ` Roger Pau Monné
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=20180212144001.jdriny2grisgjsdx@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@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).