From: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-arm@nongnu.org
Subject: Re: [PATCH v8 0/3] target/arm: Added support for SME register exposure to GDB
Date: Tue, 16 Sep 2025 09:43:26 -0400 [thread overview]
Message-ID: <CAEWVDmvZDJnfz47NBGs3HDkAmQL4y-1Pujs3diUOm1UUvgPMcg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-xdREOLGyQkeeE1SxAH+27G9aepjD8jGoEJTbcLrm4+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]
Noted, thank you!
On Tue, Sep 16, 2025 at 6:39 AM Peter Maydell <peter.maydell@linaro.org>
wrote:
> On Tue, 9 Sept 2025 at 17:10, Vacha Bhavsar
> <vacha.bhavsar@oss.qualcomm.com> 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.
> >
> > Additionally, 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.
> >
> > We have chosen to drop the patch related to changing GDBState's line_buf
> > to a dynamically re-sizeable GString for the time being.
> >
> > This patch also includes a test case for testing SME register exposure
> > to GDB, based off of the existing SVE test case for the gdbstub.
> >
> > Vacha Bhavsar (3):
> > target/arm: Increase MAX_PACKET_LENGTH for SME ZA remote gdb debugging
> > target/arm: Added support for SME register exposure to GDB
> > target/arm: Added test case for SME register exposure to GDB
>
> Thanks, I have applied this version to target-arm.next.
>
> I had to fix up quite a few style nits reported by scripts/checkpatch.pl:
> for future contributions I would suggest running your patches through
> it. The script is not infallible so you have to use some judgement
> in deciding whether to make changes, but it catches simple issues
> like trailing whitespace or mixing tabs and spaces in indentation.
>
> -- PMM
>
[-- Attachment #2: Type: text/html, Size: 2711 bytes --]
prev parent reply other threads:[~2025-09-16 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 16:10 [PATCH v8 0/3] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-09-09 16:10 ` [PATCH v8 1/3] target/arm: Increase MAX_PACKET_LENGTH for SME ZA remote gdb debugging Vacha Bhavsar
2025-09-09 16:10 ` [PATCH v8 2/3] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-09-09 16:10 ` [PATCH v8 3/3] target/arm: Added test case " Vacha Bhavsar
2025-09-16 10:39 ` [PATCH v8 0/3] target/arm: Added support " Peter Maydell
2025-09-16 13:43 ` Vacha Bhavsar [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=CAEWVDmvZDJnfz47NBGs3HDkAmQL4y-1Pujs3diUOm1UUvgPMcg@mail.gmail.com \
--to=vacha.bhavsar@oss.qualcomm.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).