From: Thiago Jung Bauermann via Gdb <gdb@sourceware.org>
To: Luis <luis.machado.foss@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
gdb@sourceware.org,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: Re: gdb support for SME-without-SVE ?
Date: Wed, 28 Jan 2026 04:23:59 +0000 [thread overview]
Message-ID: <87ldhigyao.fsf@linaro.org> (raw)
In-Reply-To: <CANnS9rsG2r8Ufwa0MoUjRVowrM44eS5NOUNpduFCuKm1aEgmdA@mail.gmail.com> (Luis's message of "Wed, 28 Jan 2026 01:07:43 +0000")
Hello,
I'm currently implementing SME-only (i.e. without SVE) support in GDB
for Linux userspace debugging. It's mostly done, I just need to test a
few things, polish the code and prepare the patches. I'm hoping to send
the patches next week.
Due to the limitations in the remote protocol that Luis mentioned below,
I can't run the tests against a remote target so I'm only focusing on
local debugging, unfortunately.
Luis <luis.machado.foss@gmail.com> writes:
> On Tue, Jan 27, 2026, 21:24 Peter Maydell <peter.maydell@linaro.org> wrote:
>
> > (2) If the CPU has SME and not SVE, presumably we should still
> > expose org.gnu.gdb.aarch64.sve, as it's where the z registers are.
> > What should we report "vl" as here? How about when the CPU is not
> > in streaming mode and the z regs aren't accessible?
>
> Are there still Z registers without SVE?
Yes, but they are only accessible while in streaming mode.
For simplicity, if the inferior isn't in streaming mode I'm making the
SVE registers available in non-streaming mode (i.e., behave as if SVE is
supported) with vg = 2 as Peter mentions below. In this case, the Z
registers are equivalent to the regular vector registers.
> I don't think this is properly supported in any case. On top of that
> SVE and SME are not properly supported via the remote protocol. In
> theory it works if you don't change vg/svg mid-execution. So no SSVE
> enabling etc. But in practice it does not work well. When the vg/svg
> size changes you end up with overruns or garbage.
>
> The initial implementation of SVE assumed remote debugging wasn't
> important. We're stuck with that until remote protocol enhancements
> are contributed.
>
> Those enhancements have been proposed multiple times but there were
> always downsides and it tends to die and fall into limbo. It mostly
> only affects SVE and SME. Maybe AMX.
I'm planning to resume this work again in the next few months. Christina
and Klaus from Intel came up with a nice proposal.
--
Thiago
next prev parent reply other threads:[~2026-01-28 4:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:31 Peter Maydell via Gdb
2026-01-27 14:21 ` Simon Marchi via Gdb
2026-01-27 14:47 ` Peter Maydell via Gdb
2026-01-27 14:57 ` Simon Marchi via Gdb
2026-01-27 21:23 ` Peter Maydell via Gdb
2026-01-27 21:28 ` Simon Marchi via Gdb
2026-01-28 1:07 ` Luis via Gdb
2026-01-28 4:23 ` Thiago Jung Bauermann via Gdb [this message]
2026-01-28 8:02 ` Luis via Gdb
2026-01-28 16:20 ` Peter Maydell via Gdb
2026-01-29 4:12 ` Thiago Jung Bauermann via Gdb
2026-01-29 9:10 ` Peter Maydell via Gdb
2026-01-29 11:34 ` Peter Maydell via Gdb
2026-01-30 4:28 ` Thiago Jung Bauermann via Gdb
2026-01-30 9:41 ` Peter Maydell via Gdb
2026-01-30 12:29 ` Peter Maydell via Gdb
2026-01-30 16:16 ` Thiago Jung Bauermann via Gdb
2026-01-30 16:29 ` Peter Maydell via Gdb
2026-01-30 17:06 ` Thiago Jung Bauermann via Gdb
2026-01-30 17:17 ` Peter Maydell via Gdb
2026-01-30 18:18 ` Thiago Jung Bauermann via Gdb
2026-01-30 18:34 ` Peter Maydell via Gdb
2026-01-30 18:40 ` Thiago Jung Bauermann via Gdb
2026-01-30 18:59 ` Peter Maydell via Gdb
2026-01-30 18:59 ` Thiago Jung Bauermann via Gdb
2026-01-30 19:01 ` Peter Maydell via Gdb
2026-01-30 19:03 ` Thiago Jung Bauermann via Gdb
2026-02-02 11:01 ` Peter Maydell via Gdb
2026-02-02 14:06 ` Peter Maydell via Gdb
2026-02-02 20:43 ` Thiago Jung Bauermann via Gdb
2026-01-30 18:24 ` Luis via Gdb
2026-01-27 21:29 ` Andrew Pinski via Gdb
2026-01-28 0:42 ` Luis via Gdb
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=87ldhigyao.fsf@linaro.org \
--to=gdb@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=peter.maydell@linaro.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