From: Luis <luis.machado.foss@gmail.com>
To: Ezra.Sitorus@arm.com, gdb-patches@sourceware.org
Cc: thiago.bauermann@linaro.org
Subject: Re: [PATCH v3 3/6] gdb/aarch64: signal frame support for fpmr
Date: Mon, 27 Oct 2025 22:25:26 +0000 [thread overview]
Message-ID: <09843fcb-22d7-43f8-9eca-aea4e98b268f@gmail.com> (raw)
In-Reply-To: <20251021150300.59860-4-Ezra.Sitorus@arm.com>
On 21/10/2025 16:02, Ezra.Sitorus@arm.com wrote:
> From: Ezra Sitorus <ezra.sitorus@arm.com>
>
> Add support for FPMR in signal frames and restore contents of FPMR.
> ---
> Changes from v1->v2:
> * Addressed comments/whitespace/formatting issues.
> * gdb/arch/aarch64.h: operator() takes fpmr into account now.
> * Defined HWCAP2_FPMR in gdb/arch/aarch64.h
>
> Changes from v2-v3:
> * Formatting fixes.
> * Moved initialisation of fpmr variables closer to where they are used.
>
> Ezra
>
> gdb/aarch64-linux-tdep.c | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
> index 10b44d978af..5346ae39eda 100644
> --- a/gdb/aarch64-linux-tdep.c
> +++ b/gdb/aarch64-linux-tdep.c
> @@ -167,6 +167,7 @@
> #define AARCH64_TPIDR2_MAGIC 0x54504902
> #define AARCH64_ZT_MAGIC 0x5a544e01
> #define AARCH64_GCS_MAGIC 0x47435300
> +#define AARCH64_FPMR_MAGIC 0x46504d52
>
> /* Defines for the extra_context that follows an AARCH64_EXTRA_MAGIC. */
> #define AARCH64_EXTRA_DATAP_OFFSET 8
> @@ -213,6 +214,9 @@
> /* features_enabled value offset in the GCS signal frame context. */
> #define AARCH64_GCS_CONTEXT_FEATURES_ENABLED_OFFSET 16
>
> +/* FPMR constants. */
> +#define AARCH64_FPMR_OFFSET 8
> +
> /* Holds information about the signal frame. */
> struct aarch64_linux_sigframe
> {
> @@ -260,6 +264,12 @@ struct aarch64_linux_sigframe
> uint64_t gcspr;
> /* Flags indicating which GCS features are enabled for the thread. */
> uint64_t gcs_features_enabled;
> +
> + /* True if we have an FPMR entry in the signal context, false otherwise. */
> + bool fpmr_available = false;
> + /* FPMR value. */
> + CORE_ADDR fpmr = 0;
> +
> };
>
> /* Read an aarch64_ctx, returning the magic value, and setting *SIZE to the
> @@ -576,6 +586,22 @@ aarch64_linux_read_signal_frame_info (const frame_info_ptr &this_frame,
> section += size;
> break;
> }
> + case AARCH64_FPMR_MAGIC:
> + {
> + gdb_byte buf[8];
> + if (target_read_memory (section + AARCH64_FPMR_OFFSET,
> + buf, 8) != 0)
> + {
> + warning (_("Failed to read the FPMR section address from the"
> + " signal frame context."));
> + section += size;
> + break;
> + }
> + signal_frame.fpmr = extract_unsigned_integer (buf, 8, byte_order);
> + signal_frame.fpmr_available = true;
> + section += size;
> + break;
> + }
> case AARCH64_EXTRA_MAGIC:
> {
> /* Extra is always the last valid section in reserved and points to
> @@ -739,6 +765,13 @@ aarch64_linux_sigframe_init (const struct tramp_frame *self,
> }
> }
>
> + /* Handle FPMR. */
> + if (tdep->has_fpmr () && signal_frame.fpmr_available != 0)
> + {
> + trad_frame_set_reg_value (this_cache, tdep->fpmr_regnum,
> + signal_frame.fpmr);
> + }
> +
> /* Restore the tpidr2 register, if the target supports it and if there is
> an entry for it. */
> if (signal_frame.tpidr2_section != 0 && tdep->has_tls ()
> @@ -791,6 +824,7 @@ aarch64_linux_sigframe_prev_arch (const frame_info_ptr &this_frame,
> aarch64_features features = aarch64_features_from_target_desc (tdesc);
> features.vq = sve_vq_from_vl (signal_frame.vl);
> features.svq = (uint8_t) sve_vq_from_vl (signal_frame.svl);
> + features.fpmr = signal_frame.fpmr_available;
>
> struct gdbarch_info info;
> info.bfd_arch_info = bfd_lookup_arch (bfd_arch_aarch64, bfd_mach_aarch64);
This is OK. Thanks!
Approved-By: Luis Machado <luis.machado.foss@gmail.com>
next prev parent reply other threads:[~2025-10-27 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:02 [PATCH v3 0/6] gdb/aarch64: Support for FPMR Ezra.Sitorus
2025-10-21 15:02 ` [PATCH v3 1/6] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-10-27 22:32 ` Luis
2025-10-21 15:02 ` [PATCH v3 2/6] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-10-27 22:26 ` Luis
2025-10-21 15:02 ` [PATCH v3 3/6] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-10-27 22:25 ` Luis [this message]
2025-10-21 15:02 ` [PATCH v3 4/6] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-10-27 22:23 ` Luis
2025-10-21 15:02 ` [PATCH v3 5/6] gdb/aarch64: Tests " Ezra.Sitorus
2025-10-27 22:19 ` Luis
2025-10-21 15:03 ` [PATCH v3 6/6] gdb/doc: Document AArch64 FPMR support Ezra.Sitorus
2025-10-21 15:35 ` Eli Zaretskii
2025-10-22 9:25 ` Ezra Sitorus
2025-10-22 11:53 ` Eli Zaretskii
2025-10-27 22:08 ` Luis
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=09843fcb-22d7-43f8-9eca-aea4e98b268f@gmail.com \
--to=luis.machado.foss@gmail.com \
--cc=Ezra.Sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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