From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Ezra Sitorus <ezra.sitorus@arm.com>
Cc: <gdb-patches@sourceware.org>, <luis.machado.foss@gmail.com>
Subject: Re: [RFC PATCH 0/5] gdb/aarch64: Support for FPMR
Date: Fri, 12 Sep 2025 00:17:32 -0300 [thread overview]
Message-ID: <87segs2wc3.fsf@linaro.org> (raw)
In-Reply-To: <aMLwWJgWL9g-7Vog@D2G2X7XGD1> (Ezra Sitorus's message of "Thu, 11 Sep 2025 16:52:56 +0100")
Ezra Sitorus <ezra.sitorus@arm.com> writes:
>> Hello Ezra,
>
> Hi!
>
>> Thank you for these patches.
>>
>> <Ezra.Sitorus@arm.com> writes:
>>
>> > From: Ezra Sitorus <ezra.sitorus@arm.com>
>> >
>> > The Floating Point Mode Register (FPMR) determines the behaviour of FP8
>> > instructions. This patch series adds support for this register into gdb.
>> >
>> > This has been tested using Shrinkwrap, which allows me to run Linux on a
>> > model of an Arm system with new features. You can find more information
>> > here: [1].
>>
>> Is there something specific one has to do to enable FPMR on
>> Shrinkwrap/FVP?
>>
>> I tried building an Armv9.5 configuration:
>>
>> $ shrinkwrap build --overlay=arch/v9.5.yaml ns-edk2.yaml
>>
>> and then running it with upstream kernel v6.16-rc7 which I think should
>> support FPMR, but AT_HWCAP doesn't have the FPMR bit set, and the test
>> program from the allow_aarch64_fpmr_tests procedure gets a SIGILL so the
>> testcases in this series report unsupported.
>>
>> --
>> Thiago
>
> I think that kernel version is fine. To get FPMR to work, I created an overlay.yaml
> file which contains this:
>
> run:
> params:
> -C cluster0.has_fpmr: 1
>
> Then I run with this:
>
> shrinkwrap run ns-edk2.yaml --overlay overlay.yaml
Thanks! This worked.
> FYI, if you want to enable other features, you can see the options by doing:
>
> docker exec <docker container name> FVP_Base_RevC-2xAEMvA --list-params
This is very useful. Thanks for the tip.
--
Thiago
prev parent reply other threads:[~2025-09-12 3:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:17 Ezra.Sitorus
2025-09-05 13:17 ` [RFC PATCH 1/5] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-09-07 22:55 ` Luis
2025-09-10 23:56 ` Thiago Jung Bauermann
2025-09-10 23:45 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 2/5] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-09-07 22:55 ` Luis
2025-09-10 23:46 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 3/5] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-11 0:03 ` Thiago Jung Bauermann
2025-09-10 23:47 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 4/5] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-10 23:48 ` Thiago Jung Bauermann
2025-09-05 13:17 ` [RFC PATCH 5/5] gdb/aarch64: Tests for fpmr Ezra.Sitorus
2025-09-07 22:56 ` Luis
2025-09-16 11:09 ` Ezra Sitorus
2025-09-16 23:50 ` Luis
2025-09-10 23:53 ` Thiago Jung Bauermann
2025-09-10 23:39 ` [RFC PATCH 0/5] gdb/aarch64: Support for FPMR Thiago Jung Bauermann
2025-09-11 15:52 ` Ezra Sitorus
2025-09-12 3:17 ` Thiago Jung Bauermann [this message]
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=87segs2wc3.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=ezra.sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.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