From: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
"nickc@redhat.com" <nickc@redhat.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: [GAS][AArch64] Define ETE system registers
Date: Thu, 24 Sep 2020 15:09:44 +0000 [thread overview]
Message-ID: <AM6PR08MB4581E35EAB56E881994EE488E4390@AM6PR08MB4581.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi,
This patch introduces ETE (Embedded Trace Extension) system registers.
If ETE is implemented, the ETE registers are:
- TRCEXTINSELR<0-3> an External Input Select Register <n>.
- TRCRSR a Resources Status Register.
Above system registers are documented here:
https://developer.arm.com/docs/ddi0601/f
Note: as this is register only extension, we do not want to hide these
registers behind -march flag going forward (they should be enabled by
default).
aarch64-none-linux-gnu binutils regression tests OK.
OK for master branch?
PS: I do not have write permission, can this be commited in my name if
approved please?
Kind regards,
Przemyslaw Wirkus
gas/ChangeLog:
2020-09-17 Przemyslaw Wirkus <przemyslaw.wirkus@arm.com>
* testsuite/gas/aarch64/ete.d: New test.
* testsuite/gas/aarch64/ete.s: New test.
opcodes/ChangeLog:
2020-09-17 Przemyslaw Wirkus <przemyslaw.wirkus@arm.com>
* aarch64-opc.c: Add ETE system registers TRCEXTINSELR<0-3> and TRCRSR.
[-- Attachment #2: rb13475.patch --]
[-- Type: application/octet-stream, Size: 2030 bytes --]
diff --git a/gas/testsuite/gas/aarch64/ete.d b/gas/testsuite/gas/aarch64/ete.d
new file mode 100644
index 0000000000000000000000000000000000000000..511b4fb5343871aba144036505029891efa8d850
--- /dev/null
+++ b/gas/testsuite/gas/aarch64/ete.d
@@ -0,0 +1,18 @@
+#name: ETE System registers
+#objdump: -dr
+
+.*: file format .*
+
+Disassembly of section \.text:
+
+0+ <.*>:
+[^:]+: d5310880 mrs x0, trcextinselr0
+[^:]+: d5310980 mrs x0, trcextinselr1
+[^:]+: d5310a80 mrs x0, trcextinselr2
+[^:]+: d5310b80 mrs x0, trcextinselr3
+[^:]+: d5310a00 mrs x0, trcrsr
+[^:]+: d5110880 msr trcextinselr0, x0
+[^:]+: d5110980 msr trcextinselr1, x0
+[^:]+: d5110a80 msr trcextinselr2, x0
+[^:]+: d5110b80 msr trcextinselr3, x0
+[^:]+: d5110a00 msr trcrsr, x0
diff --git a/gas/testsuite/gas/aarch64/ete.s b/gas/testsuite/gas/aarch64/ete.s
new file mode 100644
index 0000000000000000000000000000000000000000..72720eed9ee3d4e5a1c82e93def32d59cf2601b4
--- /dev/null
+++ b/gas/testsuite/gas/aarch64/ete.s
@@ -0,0 +1,15 @@
+/* ETE System registers. */
+
+/* Read from system register. */
+mrs x0, trcextinselr0
+mrs x0, trcextinselr1
+mrs x0, trcextinselr2
+mrs x0, trcextinselr3
+mrs x0, trcrsr
+
+/* Write to system register. */
+msr trcextinselr0, x0
+msr trcextinselr1, x0
+msr trcextinselr2, x0
+msr trcextinselr3, x0
+msr trcrsr, x0
diff --git a/opcodes/aarch64-opc.c b/opcodes/aarch64-opc.c
index 1be8d21642be6cce1ecebb01e6147ea63fe209b8..83afb1f9778ab7cff8f2105c95999e83847f89d7 100644
--- a/opcodes/aarch64-opc.c
+++ b/opcodes/aarch64-opc.c
@@ -4319,6 +4319,12 @@ const aarch64_sys_reg aarch64_sys_regs [] =
SR_CORE("trbsr_el1", CPENC (3,0,C9,C11,3), 0),
SR_CORE("trbtrg_el1", CPENC (3,0,C9,C11,6), 0),
+ SR_CORE ("trcextinselr0", CPENC (2,1,C0,C8,4), 0),
+ SR_CORE ("trcextinselr1", CPENC (2,1,C0,C9,4), 0),
+ SR_CORE ("trcextinselr2", CPENC (2,1,C0,C10,4), 0),
+ SR_CORE ("trcextinselr3", CPENC (2,1,C0,C11,4), 0),
+ SR_CORE ("trcrsr", CPENC (2,1,C0,C10,0), 0),
+
{ 0, CPENC (0,0,0,0,0), 0, 0 }
};
next reply other threads:[~2020-09-24 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 15:09 Przemyslaw Wirkus [this message]
2020-09-28 14:43 ` Nick Clifton
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=AM6PR08MB4581E35EAB56E881994EE488E4390@AM6PR08MB4581.eurprd08.prod.outlook.com \
--to=przemyslaw.wirkus@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).