Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Luis <luis.machado.foss@gmail.com>,
	 gdb-patches@sourceware.org,
	 Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: Re: [PATCH] docs: Clarify gdb remote protocol AArch64 SVE and SME handling
Date: Fri, 20 Mar 2026 00:02:18 -0300	[thread overview]
Message-ID: <87ldfn6w5h.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA-8BtFZUicFvjQEDoKo_FgWco4e2bP_D0J2-J8r1JOdYw@mail.gmail.com> (Peter Maydell's message of "Thu, 19 Mar 2026 13:41:16 +0000")

Hello,

Peter Maydell <peter.maydell@linaro.org> writes:

> On Mon, 2 Feb 2026 at 23:41, Luis <luis.machado.foss@gmail.com> wrote:
>>
>> Hi,
>>
>>
>> On 30/01/2026 09:36, Peter Maydell wrote:
>> > On Thu, 29 Jan 2026 at 23:18, Luis <luis.machado.foss@gmail.com> wrote:
>> >> I don't feel comfortable setting this is stone before we have a
>> >> patch that clarifies how this separation between SVE and SME is
>> >> achieved.
>> >
>> > I agree that we don't want to commit this until we're happy that
>> > it's the right thing. This patch is my attempt to put down in a
>> > concrete form how I think this should work.
>> >
>> > When you talk about "a patch that clarifies how this separation
>> > between SVE and SME is achieved", what do you mean? A patch to
>> > gdb? With this proposal, current gdb I think should work without
>> > changes. The changes Thiago has are all because of the way that
>> > the Linux ptrace API has chosen to represent SVE and SME, AIUI.
>>
>> We need a couple things from what I can see.
>>
>> First we need to teach gdb about SME without SVE, and that's what Thiago
>> is working on. I´d like to see that patch first before we adjust the
>> documentation for the SME-but-no-SVE mode. Just to make sure things match.
>
> Hi -- I just wanted to come back to this thread to ask how
> the "native (ptrace) gdb SME-no-SVE" support is going. Do
> we now have that landed, or at least solid enough that we are
> happy to update the remote-protocol documentation?

I was about to submit the patches when I ran the full GDB testsuite
(I had been running a subset during development) and found a few
regressions I need to fix. I don't expect big changes though, and
I will submit the patches soon.

The essence of the changes is that if the target has SME but not SVE,
then GDB uses a target description with SVE but with vq = 1, meaning
that the SVE register set has the same size as the FPSIMD regset.

-- 
Thiago

  reply	other threads:[~2026-03-20  3:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 18:11 Peter Maydell
2026-01-29 23:13 ` Luis
2026-01-30  9:36   ` Peter Maydell
2026-02-02 23:41     ` Luis
2026-02-09  9:36       ` Peter Maydell
2026-02-13 11:39         ` Luis
2026-02-13 12:15           ` Peter Maydell
2026-03-19 13:41       ` Peter Maydell
2026-03-20  3:02         ` Thiago Jung Bauermann [this message]
2026-03-20  9:25           ` Peter Maydell
2026-01-30 11:37 ` Eli Zaretskii

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=87ldfn6w5h.fsf@linaro.org \
    --to=thiago.bauermann@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado.foss@gmail.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=peter.maydell@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