From: Jan Beulich <jbeulich@suse.com>
To: Richard Earnshaw <rearnsha@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Ping: [PATCH] Arm64: support CLEARBHB alias
Date: Wed, 28 Sep 2022 14:00:01 +0200 [thread overview]
Message-ID: <03b04b63-3781-1fdd-8885-832647b2543b@suse.com> (raw)
In-Reply-To: <a9d71da9-0416-9c0e-83d5-6e8ed360f516@suse.com>
On 12.09.2022 10:40, Jan Beulich via Binutils wrote:
> While the Arm v8 ARM (rev I-a) still doesn't mention this alias, it is
> (typically via a macro) already in use in kernels and alike.
May I ask for feedback here? Without hearing back, I guess I'll simply
put this in some time next week.
Jan
> ---
> Diffs of generated files omitted.
>
> --- a/gas/testsuite/gas/aarch64/system.d
> +++ b/gas/testsuite/gas/aarch64/system.d
> @@ -12,6 +12,7 @@ Disassembly of section \.text:
> .*: d503207f wfi
> .*: d503209f sev
> .*: d50320bf sevl
> +.*: d50322df clearbhb
> .*: d503201f nop
> .*: d503203f yield
> .*: d503205f wfe
> @@ -34,7 +35,7 @@ Disassembly of section \.text:
> .*: d503227f hint #0x13
> .*: d503229f (hint #0x14|csdb)
> .*: d50322bf hint #0x15
> -.*: d50322df hint #0x16
> +.*: d50322df (hint #0x16|clearbhb)
> .*: d50322ff hint #0x17
> .*: d503231f (hint #0x18|paciaz)
> .*: d503233f (hint #0x19|paciasp)
> --- a/gas/testsuite/gas/aarch64/system.s
> +++ b/gas/testsuite/gas/aarch64/system.s
> @@ -11,6 +11,7 @@
> wfi
> sev
> sevl
> + clearbhb
>
> .macro all_hints from=0, to=127
> hint \from
> --- a/opcodes/aarch64-tbl.h
> +++ b/opcodes/aarch64-tbl.h
> @@ -4034,6 +4034,7 @@ const struct aarch64_opcode aarch64_opco
> CORE_INSN ("esb", 0xd503221f, 0xffffffff, ic_system, 0, OP0 (), {}, F_ALIAS),
> CORE_INSN ("psb", 0xd503223f, 0xffffffff, ic_system, 0, OP1 (BARRIER_PSB), {}, F_ALIAS),
> CORE_INSN ("tsb", 0xd503225f, 0xffffffff, ic_system, 0, OP1 (BARRIER_PSB), {}, F_ALIAS),
> + CORE_INSN ("clearbhb", 0xd50322df, 0xffffffff, ic_system, 0, OP0 (), {}, F_ALIAS),
> CORE_INSN ("clrex", 0xd503305f, 0xfffff0ff, ic_system, 0, OP1 (UIMM4), {}, F_OPD0_OPT | F_DEFAULT (0xF)),
> CORE_INSN ("dsb", 0xd503309f, 0xfffff0ff, ic_system, 0, OP1 (BARRIER), {}, F_HAS_ALIAS),
> V8_7_INSN ("dsb", 0xd503323f, 0xfffff3ff, ic_system, OP1 (BARRIER_DSB_NXS), {}, F_HAS_ALIAS),
next prev parent reply other threads:[~2022-09-28 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:40 Jan Beulich
2022-09-28 12:00 ` Jan Beulich [this message]
2022-10-05 17:48 ` Ping: " Richard Earnshaw
2022-10-06 6:06 ` 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=03b04b63-3781-1fdd-8885-832647b2543b@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=rearnsha@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).