From: Luis Machado <luis.machado@arm.com>
To: binutils@sourceware.org
Subject: [PING v1][PATCH] [aarch64/sme] binutils: Add new NT_ARM_ZA and NT_ARM_SSVE register set constants
Date: Wed, 28 Dec 2022 18:07:11 +0000 [thread overview]
Message-ID: <47b95434-48df-6509-a0f0-7b1644de0359@arm.com> (raw)
In-Reply-To: <20221219131149.2268979-1-luis.machado@arm.com>
On 12/19/22 13:11, Luis Machado via Binutils wrote:
> From: Ezra Sitorus <ezra.sitorus@arm.com>
>
> The AArch64 SME feature exposes a couple new register sets: NT_ARM_ZA and
> NT_ARM_SSVE.
>
> Teach binutils/include about those.
>
> Co-authored-by: Luis Machado <luis.machado@arm.com>
> ---
> binutils/readelf.c | 4 ++++
> include/elf/common.h | 5 +++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/binutils/readelf.c b/binutils/readelf.c
> index bce93782952..96e9502318a 100644
> --- a/binutils/readelf.c
> +++ b/binutils/readelf.c
> @@ -19547,6 +19547,10 @@ get_note_type (Filedata * filedata, unsigned e_type)
> return _("NT_ARM_PACG_KEYS (ARM pointer authentication generic keys)");
> case NT_ARM_TAGGED_ADDR_CTRL:
> return _("NT_ARM_TAGGED_ADDR_CTRL (AArch tagged address control)");
> + case NT_ARM_SSVE:
> + return _("NT_ARM_SSVE (AArch64 streaming SVE registers)");
> + case NT_ARM_ZA:
> + return _("NT_ARM_ZA (AArch64 SME ZA register)");
> case NT_ARM_PAC_ENABLED_KEYS:
> return _("NT_ARM_PAC_ENABLED_KEYS (AArch64 pointer authentication enabled keys)");
> case NT_ARC_V2:
> diff --git a/include/elf/common.h b/include/elf/common.h
> index 16587f6fb06..c935746148e 100644
> --- a/include/elf/common.h
> +++ b/include/elf/common.h
> @@ -696,6 +696,11 @@
> #define NT_ARM_PAC_ENABLED_KEYS 0x40a /* AArch64 pointer authentication
> enabled keys (prctl()) */
> /* note name must be "LINUX". */
> +#define NT_ARM_SSVE 0x40b /* AArch64 SME streaming SVE
> + registers. */
> + /* note name must be "LINUX". */
> +#define NT_ARM_ZA 0x40c /* AArch64 SME ZA register. */
> + /* note name must be "LINUX". */
> #define NT_ARC_V2 0x600 /* ARC HS accumulator/extra registers. */
> /* note name must be "LINUX". */
> #define NT_LARCH_CPUCFG 0xa00 /* LoongArch CPU config registers */
next prev parent reply other threads:[~2022-12-28 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 13:11 [PATCH] " Luis Machado
2022-12-28 18:07 ` Luis Machado [this message]
2023-01-03 11:16 ` [PING v1][PATCH] " Nick Clifton
2023-01-04 5:40 ` Luis Machado
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=47b95434-48df-6509-a0f0-7b1644de0359@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).