From: Matthieu Longo <matthieu.longo@arm.com>
To: <binutils@sourceware.org>
Cc: Richard Earnshaw <richard.earnshaw@arm.com>,
Nick Clifton <nickc@redhat.com>,
Matthieu Longo <matthieu.longo@arm.com>
Subject: [PATCH v1 0/4] aarch64: add new Armv9.5-A features and their associated registers (RAS, Debug, Performance Monitor)
Date: Thu, 4 Jul 2024 15:23:34 +0100 [thread overview]
Message-ID: <20240704142338.1582659-1-matthieu.longo@arm.com> (raw)
Hi,
[patch 0/4] aarch64: aarch64: add new Armv9.5-A features and their associated registers (RAS, Debug, Performance Monitor)
[patch v1 1/4] aarch64: add E3DSE feature and its associated registers
[patch v1 2/4] aarch64: add SPMU2 feature and its associated registers
[patch v1 3/4] aarch64: add STEP2 feature and its associated registers
[patch v1 4/4] aarch64: add Debug Feature Register 2 (ID_AA64DFR2_EL1)
AArch64 defines new registers for Armv9.5-A architecture.
This patch series adds the following features and their associated system registers:
- e3dse (Delegated SError exceptions for EL3)
- fpmu2 (System Performance Monitors Extension version 2)
- step2 (Enhanced Software Step Extension)
- ID_AA64DFR2_EL1 (Debug Feature Register 2)
Each patch also adds relevant tests.
Regression tested on aarch64-none-elf, and no regression found.
Ok for binutils-master?
Regards,
Matthieu.
Link to V0 posting: https://sourceware.org/pipermail/binutils/2024-June/135226.html
Revision 1:
- Split id_aa64dfr2_el1 from the registers for STEP2 feature.
- Add test for id_aa64dfr2_el1 and its friends.
Matthieu Longo (4):
aarch64: add E3DSE feature and its associated registers
aarch64: add SPMU2 feature and its associated registers
aarch64: add STEP2 feature and its associated registers
aarch64: add Debug Feature Register 2 (ID_AA64DFR2_EL1)
.../armv9_5-a-sysregs-archv9_4-unsupported.d | 3 +++
.../armv9_5-a-sysregs-archv9_4-unsupported.l | 17 +++++++++++++++++
.../gas/aarch64/sysreg/armv9_5-a-sysregs.d | 17 +++++++++++++++++
.../gas/aarch64/sysreg/armv9_5-a-sysregs.s | 13 +++++++++++++
gas/testsuite/gas/aarch64/sysreg/sysreg.d | 5 +++++
gas/testsuite/gas/aarch64/sysreg/sysreg.s | 5 +++++
include/opcode/aarch64.h | 12 +++++++++++-
opcodes/aarch64-sys-regs.def | 5 +++++
8 files changed, 76 insertions(+), 1 deletion(-)
create mode 100644 gas/testsuite/gas/aarch64/sysreg/armv9_5-a-sysregs-archv9_4-unsupported.d
create mode 100644 gas/testsuite/gas/aarch64/sysreg/armv9_5-a-sysregs-archv9_4-unsupported.l
create mode 100644 gas/testsuite/gas/aarch64/sysreg/armv9_5-a-sysregs.d
create mode 100644 gas/testsuite/gas/aarch64/sysreg/armv9_5-a-sysregs.s
--
2.45.1
next reply other threads:[~2024-07-04 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 14:23 Matthieu Longo [this message]
2024-07-04 14:23 ` [PATCH v1 1/4] aarch64: add E3DSE feature and its associated registers Matthieu Longo
2024-07-04 14:23 ` [PATCH v1 2/4] aarch64: add SPMU2 " Matthieu Longo
2024-07-04 14:23 ` [PATCH v1 3/4] aarch64: add STEP2 " Matthieu Longo
2024-07-04 14:23 ` [PATCH v1 4/4] aarch64: add Debug Feature Register 2 (ID_AA64DFR2_EL1) Matthieu Longo
2024-07-05 12:20 ` [PATCH v1 0/4] aarch64: add new Armv9.5-A features and their associated registers (RAS, Debug, Performance Monitor) Richard Earnshaw (lists)
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=20240704142338.1582659-1-matthieu.longo@arm.com \
--to=matthieu.longo@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=richard.earnshaw@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).