From: "Alex Bennée" <alex.bennee@linaro.org>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] gdbstub: update aarch64-core.xml
Date: Mon, 19 May 2025 17:05:53 +0100 [thread overview]
Message-ID: <87r00kr3fi.fsf@draig.linaro.org> (raw)
In-Reply-To: <swih62.nwehumxno4zp@linaro.org> (Manos Pitsidianakis's message of "Mon, 19 May 2025 16:45:21 +0300")
Manos Pitsidianakis <manos.pitsidianakis@linaro.org> writes:
> On Mon, 19 May 2025 15:55, Alex Bennée <alex.bennee@linaro.org> wrote:
>>Manos Pitsidianakis <manos.pitsidianakis@linaro.org> writes:
>>
>>> Update aarch64-core.xml to include field definitions for PSTATE, which
>>> in gdb is modelled in the cpsr (current program status register)
>>> pseudo-register, named after the actual cpsr register in armv7.
>>>
>>> Defining the fields layout of the register allows easy inspection of for
>>> example, the current exception level (EL):
>>>
>>> For example. Before booting a Linux guest, EL=2, but after booting and
>>> Ctrl-C'ing in gdb, we get EL=0:
>>>
>>> (gdb) info registers $cpsr
>>> cpsr 0x20402009 [ SP EL=2 BTYPE=0 PAN C ]
>>> (gdb) cont
>>> Continuing.
>>> ^C
>>> Thread 2 received signal SIGINT, Interrupt.
>>> 0x0000ffffaaff286c in ?? ()
>>> (gdb) info registers $cpsr
>>> cpsr 0x20001000 [ EL=0 BTYPE=0 SSBS C ]
>>>
>>> The aarch64-core.xml has been updated to match exactly the version
>>> retrieved from upstream gdb, retrieved in 2025-05-19 from HEAD commit
>>> 9f4dc0b137c86f6ff2098cb1ab69442c69d6023d.
>>>
>>> https://sourceware.org/git/?p=binutils-gdb.git;a=tree;h=9f4dc0b137c86f6ff2098cb1ab69442c69d6023d
>>>
>>> Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
>>
>>Queued to gdbstub/next, thanks.
>>
>
> Would patches for the field system registers (NZCV, CurrentEL, DAIF,
> SPSel) be acceptable?
>
> If yes, I think defining them in the static core xml is cleaner than
> generating them dynamically in "system-registers.xml" like we do with
> arm_gen_dynamic_sysreg_feature() but both can work. The drawback would
> be that we wouldn't match upstream gdb's core xml schema anymore. (Maybe
> we can add a new xml include "pstate.xml" instead)
You could submit to the gdb core schema first (surely they would also
benefit from the patch?).
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2025-05-19 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 11:01 [PATCH] gdbstub: update aarch64-core.xml Manos Pitsidianakis
2025-05-19 12:55 ` Alex Bennée
2025-05-19 13:45 ` Manos Pitsidianakis
2025-05-19 16:05 ` Alex Bennée [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=87r00kr3fi.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).