Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann via Gdb <gdb@sourceware.org>
To: Peter Maydell <peter.maydell@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: Mon, 02 Feb 2026 20:43:24 +0000	[thread overview]
Message-ID: <87343ilvv7.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA_hWWLtSAiNNMLP_nQUpveKBnAB4tsC2uZF-jyW+rbB3g@mail.gmail.com> (Peter Maydell's message of "Mon, 2 Feb 2026 14:06:11 +0000")

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

> On Mon, 2 Feb 2026 at 11:01, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Fri, 30 Jan 2026 at 19:01, Peter Maydell <peter.maydell@linaro.org> wrote:
>> >
>> > On Fri, 30 Jan 2026 at 18:59, Thiago Jung Bauermann
>> > <thiago.bauermann@linaro.org> wrote:
>> > > I was able to enable SME2p1 by adding these options:
>> > >
>> > >     -C cluster0.sve.sme2_version : 1
>> > >     -C cluster1.sve.sme2_version : 1
>> > >
>> > > Now my features list shows sme2p1:
>> > >
>> > > Features        : fp asimd evtstrm crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop asimddp asimdfhm dit uscat ilrcpc flagm sb paca pacg gcs dcpodp flagm2 frint i8mm bf16 dgh rng bti ecv afp sme smei16i64 smef64f64 smei8i32 smef16f32 smeb16f32 smef32f32 wfxt ebf16 cssc sme2 sme2p1 smei16i32 smebi32i32 mops hbc poe lsfe
>> > >
>> > > I still get only passes in the testcase, but more tests were run now:
>> > >
>> > >                 === gdb Summary ===
>> > >
>> > > # of expected passes            286
>> > >
>> > > The sme2_version option goes all the way to SME2p3, but I didn't try
>> > > that one.
>> >
>> > Great -- this must be a QEMU issue.
>>
>> I figured out what happens here -- if you use "-cpu max,sme=on"
>> a QEMU bug means this messes up the ID register value passed to the
>> guest (it forces the SME field in the register to 1, downgrading
>> it from SME2 to a weird thing that confuses the guest kernel).
>> If you stick to "-cpu max,sve=off" with no 'sme=on' part (relying
>> on the 'max' default being "SME2 is present") then you can get the
>> full set of 286 passes.
>>
>> I'll fix the QEMU handling of the option, but in the meantime
>> you can use that as a workaround if you want.
>
> ...and I have now pushed an sme-no-sve-3 branch to my gitlab
> QEMU repo which fixes the sme=on option handling and a few other
> minor things:
>
> https://gitlab.com/pm215/qemu/-/commits/sme-no-sve-3

Great! Now the results from the GDB SME tests (running all
aarch64-sme*.exp tests, not only the sanity one) match what I get with
the FVP. I get some failures, but they are problems with my GDB branch.

This branch works fine for me.

-- 
Thiago

  reply	other threads:[~2026-02-02 20:44 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
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 [this message]
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=87343ilvv7.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