From: Peter Maydell via Gdb <gdb@sourceware.org>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: Luis <luis.machado.foss@gmail.com>,
gdb@sourceware.org,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: Re: gdb support for SME-without-SVE ?
Date: Thu, 29 Jan 2026 11:34:19 +0000 [thread overview]
Message-ID: <CAFEAcA8U48phwPk+PhBxJn7SPYffcQGjE8db_m09EfdejMWwTQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-ZW0LrHhM0Jk4tjzeTL=bNwFZmgW5409pHfOhzSwgPsg@mail.gmail.com>
On Thu, 29 Jan 2026 at 09:10, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Thu, 29 Jan 2026 at 04:12, Thiago Jung Bauermann
> <thiago.bauermann@linaro.org> wrote:
> >
> > Peter Maydell <peter.maydell@linaro.org> writes:
> >
> > > On Wed, 28 Jan 2026 at 04:24, Thiago Jung Bauermann
> > > <thiago.bauermann@linaro.org> wrote:
> > >> 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.
> > >
> > > Let me know if a QEMU setup emulating "SME only" would be helpful
> > > for you with that.
> >
> > It would indeed! If there's a branch I can build, it would make my
> > testing quicker, and the regression testing more complete.
>
> I'll get one sorted out later today (the patches I have right now
> have a few issues I need to fix).
This branch:
https://gitlab.com/pm215/qemu/-/commits/sme-no-sve
should let you create an SME-only CPU with "-cpu max,sve=off".
I have not given it much more than a very cursory testing, so
let me know if you run into any problems with it.
thanks
-- PMM
next prev parent reply other threads:[~2026-01-29 11:35 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
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 [this message]
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=CAFEAcA8U48phwPk+PhBxJn7SPYffcQGjE8db_m09EfdejMWwTQ@mail.gmail.com \
--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