From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
Subject: Re: [PATCH v2 3/3] tests/tcg/aarch64: Add test case for SME2 gdbstub registers
Date: Thu, 23 Oct 2025 13:51:13 +0100 [thread overview]
Message-ID: <CAFEAcA8BobzAHpgQ3p=UVN3p0Hm1_P_xr8AN=sJ0GQtFP98FEA@mail.gmail.com> (raw)
In-Reply-To: <20251017153027.969016-4-peter.maydell@linaro.org>
On Fri, 17 Oct 2025 at 16:30, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> Test the SME2 register exposure over gdbstub, in the same way
> we already do for SME.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> +def run_test():
> + """Test reads and writes of the SME2 registers"""
> + frame = gdb.selected_frame()
> + rname = "zt0"
> + zt0 = frame.read_register(rname)
> + report(True, "Reading %s" % rname)
> +
> + # Writing to the ZT0 register, byte by byte.
> + for i in range(0, 64):
> + cmd = "set $zt0[%d] = 0x01" % (i)
> + gdb.execute(cmd)
> + report(True, "%s" % cmd)
These two lines are wrongly indented, and Python will error
out with "unexpected indent". I fixed this up in my local
tree but clearly forgot to commit the change to git before
sending. I'll fix this up in applying them to target-arm.next.
-- PMM
prev parent reply other threads:[~2025-10-23 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 15:30 [PATCH v2 0/3] target/arm: Support SME2 in gdbstub Peter Maydell
2025-10-17 15:30 ` [PATCH v2 1/3] target/arm: Implement SME2 support " Peter Maydell
2025-10-17 15:45 ` Richard Henderson
2025-10-20 20:13 ` Philippe Mathieu-Daudé
2025-10-17 15:30 ` [PATCH v2 2/3] target/arm: Implement org.gnu.gdb.aarch64.tls XML feature " Peter Maydell
2025-10-17 15:39 ` Richard Henderson
2025-10-17 15:30 ` [PATCH v2 3/3] tests/tcg/aarch64: Add test case for SME2 gdbstub registers Peter Maydell
2025-10-17 15:41 ` Richard Henderson
2025-10-20 20:14 ` Philippe Mathieu-Daudé
2025-10-23 12:51 ` Peter Maydell [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='CAFEAcA8BobzAHpgQ3p=UVN3p0Hm1_P_xr8AN=sJ0GQtFP98FEA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vacha.bhavsar@oss.qualcomm.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).