From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 07/16] [gdbserver/aarch64] sme: Add support for SME
Date: Sat, 26 Aug 2023 22:32:32 -0300 [thread overview]
Message-ID: <87y1hxjmmn.fsf@linaro.org> (raw)
In-Reply-To: <20230822112130.1513216-8-luis.machado@arm.com>
Hello Luis,
After reviewing the SME2 patches, I spotted this suggestion that
I didn't notice when I reviewed v3. Sorry about that again.
Luis Machado <luis.machado@arm.com> writes:
> +/* Wrapper for aarch64_za_regs_copy_to_reg_buf, to help copying NT_ARM_ZA
> + state from the thread (BUF) to the register cache. */
> +
> +static void
> +aarch64_za_regs_copy_to_regcache (struct regcache *regcache,
> + ATTRIBUTE_UNUSED const void *buf)
> +{
> + /* BUF is unused here since we collect the data straight from a ptrace
> + request, therefore bypassing gdbserver's own call to ptrace. */
> + int tid = lwpid_of (current_thread);
> +
> + gdb::optional<int> za_regnum
> + = find_regno_no_throw (regcache->tdesc, "za");
> + gdb::optional<int> svg_regnum
> + = find_regno_no_throw (regcache->tdesc, "svg");
> + gdb::optional<int> svcr_regnum
> + = find_regno_no_throw (regcache->tdesc, "svcr");
> +
> + gdb_assert (za_regnum.has_value ());
> + gdb_assert (svg_regnum.has_value ());
> + gdb_assert (svcr_regnum.has_value ());
By changing to find_regno() then this gdb_assert() becomes unnecessary.
> +
> + /* Update the register cache. aarch64_za_regs_copy_to_reg_buf handles
> + fetching the NT_ARM_ZA state from thread TID. */
> + aarch64_za_regs_copy_to_reg_buf (tid, regcache, *za_regnum, *svg_regnum,
> + *svcr_regnum);
> +}
> +
> +/* Wrapper for aarch64_za_regs_copy_from_reg_buf, to help copying NT_ARM_ZA
> + state from the register cache to the thread (BUF). */
> +
> +static void
> +aarch64_za_regs_copy_from_regcache (struct regcache *regcache, void *buf)
> +{
> + int tid = lwpid_of (current_thread);
> +
> + gdb::optional<int> za_regnum
> + = find_regno_no_throw (regcache->tdesc, "za");
> + gdb::optional<int> svg_regnum
> + = find_regno_no_throw (regcache->tdesc, "svg");
> + gdb::optional<int> svcr_regnum
> + = find_regno_no_throw (regcache->tdesc, "svcr");
> +
> + gdb_assert (za_regnum.has_value ());
> + gdb_assert (svg_regnum.has_value ());
> + gdb_assert (svcr_regnum.has_value ());
Same comment about find_regno().
> +
> + /* Update the thread NT_ARM_ZA state. aarch64_za_regs_copy_from_reg_buf
> + handles writing the ZA state back to thread TID. */
> + aarch64_za_regs_copy_from_reg_buf (tid, regcache, *za_regnum, *svg_regnum,
> + *svcr_regnum);
> +
> + /* We need to return the expected data in BUF, so copy whatever the kernel
> + already has to BUF. */
> +
> + /* Obtain a dump of ZA from ptrace. */
> + gdb::byte_vector za_state = aarch64_fetch_za_regset (tid);
> + memcpy (buf, za_state.data (), za_state.size ());
> +}
--
Thiago
next prev parent reply other threads:[~2023-08-27 1:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 11:21 [PATCH v4 00/16] SME support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-08-22 11:21 ` [PATCH v4 01/16] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux Luis Machado
2023-08-22 11:21 ` [PATCH v4 02/16] [gdb/aarch64] refactor: Rename SVE-specific files Luis Machado
2023-08-22 11:21 ` [PATCH v4 03/16] [gdb/gdbserver] refactor: Simplify SVE interface to read/write registers Luis Machado
2023-08-22 11:21 ` [PATCH v4 04/16] [gdb/aarch64] sve: Fix return command when using V registers in a SVE-enabled target Luis Machado
2023-08-22 11:21 ` [PATCH v4 05/16] [gdb/aarch64] sme: Enable SME registers and pseudo-registers Luis Machado
2023-08-22 11:21 ` [PATCH v4 06/16] [gdbserver/aarch64] refactor: Adjust expedited registers dynamically Luis Machado
2023-08-22 11:21 ` [PATCH v4 07/16] [gdbserver/aarch64] sme: Add support for SME Luis Machado
2023-08-27 1:32 ` Thiago Jung Bauermann [this message]
2023-08-30 10:37 ` Luis Machado
2023-08-22 11:21 ` [PATCH v4 08/16] [gdb/aarch64] sve: Fix signal frame z/v register restore Luis Machado
2023-08-22 11:21 ` [PATCH v4 09/16] [gdb/aarch64] sme: Signal frame support Luis Machado
2023-08-22 11:21 ` [PATCH v4 10/16] [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes Luis Machado
2023-08-22 11:21 ` [PATCH v4 11/16] [gdb/aarch64] sme: Support TPIDR2 signal frame context Luis Machado
2023-08-22 11:21 ` [PATCH v4 12/16] [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping register state to core files Luis Machado
2023-08-22 11:21 ` [PATCH v4 13/16] [gdb/generic] corefile/bug: Fixup (gcore) core file target description reading order Luis Machado
2023-08-22 11:21 ` [PATCH v4 14/16] [gdb/aarch64] sme: Core file support for Linux Luis Machado
2023-08-25 23:33 ` Thiago Jung Bauermann
2023-08-30 10:28 ` Luis Machado
2023-08-22 11:21 ` [PATCH v4 15/16] [gdb/testsuite] sme: Add SVE/SME testcases Luis Machado
2023-08-22 11:21 ` [PATCH v4 16/16] [gdb/docs] sme: Document SME registers and features Luis Machado
2023-08-22 11:31 ` Eli Zaretskii
2023-08-22 11:39 ` Luis Machado
2023-08-22 11:56 ` Luis Machado
2023-08-22 12:37 ` Eli Zaretskii
2023-08-25 23:35 ` [PATCH v4 00/16] SME support for AArch64 gdb/gdbserver on Linux Thiago Jung Bauermann
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=87y1hxjmmn.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).