From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, Gustavo Romero <gustavo.romero@linaro.org>
Subject: Re: [PATCH v4 0/2] target/arm: Added support for SME register exposure to GDB
Date: Wed, 23 Jul 2025 13:54:16 +0200 [thread overview]
Message-ID: <78f613a6-dd60-4f76-bbb4-8ba4fb91a7a2@linaro.org> (raw)
In-Reply-To: <20250722201404.2368507-1-vacha.bhavsar@oss.qualcomm.com>
Cc'ing Gustavo.
On 22/7/25 22:14, Vacha Bhavsar wrote:
> The QEMU GDB stub does not expose the ZA storage SME register to GDB via
> the remote serial protocol, which can be a useful functionality to debug SME
> code. To provide this functionality in Aarch64 target, this patch registers the
> SME register set with the GDB stub. To do so, this patch implements the
> aarch64_gdb_get_sme_reg() and aarch64_gdb_set_sme_reg() functions to
> specify how to get and set the SME registers, and the
> arm_gen_dynamic_smereg_feature() function to generate the target
> description in XML format to indicate the target architecture supports SME.
> Finally, this patch includes a dyn_smereg_feature structure to hold this
> GDB XML description of the SME registers for each CPU.
>
> Furthermore, this patch series increases the value of MAX_PACKET_LENGTH
> to allow for remote GDB debugging of the ZA register when the vector
> length is maximal.
>
> Signed-off-by: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
>
> Vacha Bhavsar (2):
> target/arm: Increase MAX_PACKET_LENGTH for SME ZA remote gdb debugging
> target/arm: Added support for SME register exposure to GDB
>
prev parent reply other threads:[~2025-07-23 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 20:14 [PATCH v4 0/2] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-07-22 20:14 ` [PATCH v4 1/2] target/arm: Increase MAX_PACKET_LENGTH for SME ZA remote gdb debugging Vacha Bhavsar
2025-08-04 15:34 ` Alex Bennée
2025-08-04 16:49 ` Peter Maydell
2025-08-04 18:32 ` Alex Bennée
2025-08-04 18:38 ` Peter Maydell
2025-08-05 21:21 ` Vacha Bhavsar
2025-08-06 21:18 ` Vacha Bhavsar
2025-08-07 9:42 ` Peter Maydell
2025-08-11 19:37 ` Vacha Bhavsar
2025-07-22 20:14 ` [PATCH v4 2/2] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-08-04 15:35 ` Alex Bennée
2025-08-08 13:54 ` Vacha Bhavsar
2025-08-11 7:58 ` Alex Bennée
2025-08-11 19:37 ` Vacha Bhavsar
2025-07-23 11:54 ` Philippe Mathieu-Daudé [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=78f613a6-dd60-4f76-bbb4-8ba4fb91a7a2@linaro.org \
--to=philmd@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vacha.bhavsar@oss.qualcomm.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 NNTP newsgroup(s).