public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5 00/16] SME support for AArch64 gdb/gdbserver on Linux
Date: Wed, 13 Sep 2023 11:20:28 +0100	[thread overview]
Message-ID: <49c3c4f2-b4e2-a127-f231-741247cb6166@arm.com> (raw)
In-Reply-To: <87a5tqydti.fsf@linaro.org>

Hi,

On 9/13/23 04:03, Thiago Jung Bauermann wrote:
> 
> Hello Luis,
> 
> Luis Machado <luis.machado@arm.com> writes:
> 
>> The following series enables SME 1 (Scalable Matrix Extension) support for
>> AArch64 gdb and gdbserver.
>>
>> SME expands on SVE by having a variable-sized matrix (ZA) of dimensions
>> SVL x SVL bytes.
>>
>> The first few patches and some intermediate ones refactor the code and fix
>> issues prior to enabling SME support, and thus could go in independently.
>>
>> I've kept them in the series as they are closely/logically related.
>>
>> Luis Machado (16):
>>   [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux
>>   [gdb/aarch64] refactor: Rename SVE-specific files
>>   [gdb/gdbserver] refactor: Simplify SVE interface to read/write
>>     registers
>>   [gdb/aarch64] sve: Fix return command when using V registers in a
>>     SVE-enabled target
>>   [gdb/aarch64] sme: Enable SME registers and pseudo-registers
>>   [gdbserver/aarch64] refactor: Adjust expedited registers dynamically
>>   [gdbserver/aarch64] sme: Add support for SME
>>   [gdb/aarch64] sve: Fix signal frame z/v register restore
>>   [gdb/aarch64] sme: Signal frame support
>>   [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes
>>   [gdb/aarch64] sme: Support TPIDR2 signal frame context
>>   [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping
>>     register state to core files
>>   [gdb/generic] corefile/bug: Fixup (gcore) core file target description
>>     reading order
>>   [gdb/aarch64] sme: Core file support for Linux
>>   [gdb/testsuite] sme: Add SVE/SME testcases
>>   [gdb/docs] sme: Document SME registers and features
> 
> FWIW, I have gone through the patch series and haven't found any issues.
> Thank you for addressing my comments.
> 
> So apart from the patches where Simon found some issues:
> 
> Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> 

Thanks. I sent v6/SME1 and v4/SME2 now. If Simon is happy with the changes in v6, I plan to push
that version and also v4/SME2.

      reply	other threads:[~2023-09-13 10:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 15:20 Luis Machado
2023-09-07 15:20 ` [PATCH v5 01/16] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux Luis Machado
2023-09-07 15:20 ` [PATCH v5 02/16] [gdb/aarch64] refactor: Rename SVE-specific files Luis Machado
2023-09-07 15:20 ` [PATCH v5 03/16] [gdb/gdbserver] refactor: Simplify SVE interface to read/write registers Luis Machado
2023-09-07 15:20 ` [PATCH v5 04/16] [gdb/aarch64] sve: Fix return command when using V registers in a SVE-enabled target Luis Machado
2023-09-07 15:20 ` [PATCH v5 05/16] [gdb/aarch64] sme: Enable SME registers and pseudo-registers Luis Machado
2023-09-07 15:20 ` [PATCH v5 06/16] [gdbserver/aarch64] refactor: Adjust expedited registers dynamically Luis Machado
2023-09-08 15:35   ` Simon Marchi
2023-09-08 16:00     ` Luis Machado
2023-09-08 16:52       ` Simon Marchi
2023-09-07 15:20 ` [PATCH v5 07/16] [gdbserver/aarch64] sme: Add support for SME Luis Machado
2023-09-07 15:20 ` [PATCH v5 08/16] [gdb/aarch64] sve: Fix signal frame z/v register restore Luis Machado
2023-09-07 15:20 ` [PATCH v5 09/16] [gdb/aarch64] sme: Signal frame support Luis Machado
2023-09-07 15:20 ` [PATCH v5 10/16] [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes Luis Machado
2023-09-08 11:08   ` Luis Machado
2023-09-08 15:48     ` Simon Marchi
2023-09-08 15:51       ` Simon Marchi
2023-09-08 15:51       ` Luis Machado
2023-09-08 15:59         ` Simon Marchi
2023-09-07 15:20 ` [PATCH v5 11/16] [gdb/aarch64] sme: Support TPIDR2 signal frame context Luis Machado
2023-09-07 15:20 ` [PATCH v5 12/16] [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping register state to core files Luis Machado
2023-09-08 11:09   ` Luis Machado
2023-09-08 15:58     ` Simon Marchi
2023-09-08 16:02       ` Simon Marchi
2023-09-08 16:05       ` Luis Machado
2023-09-07 15:20 ` [PATCH v5 13/16] [gdb/generic] corefile/bug: Fixup (gcore) core file target description reading order Luis Machado
2023-09-08 11:10   ` Luis Machado
2023-09-08 17:10   ` Simon Marchi
2023-09-12  8:49     ` Luis Machado
2023-09-13 13:50       ` Simon Marchi
2023-09-13 13:57         ` Luis Machado
2023-09-07 15:20 ` [PATCH v5 14/16] [gdb/aarch64] sme: Core file support for Linux Luis Machado
2023-09-07 15:20 ` [PATCH v5 15/16] [gdb/testsuite] sme: Add SVE/SME testcases Luis Machado
2023-09-07 15:20 ` [PATCH v5 16/16] [gdb/docs] sme: Document SME registers and features Luis Machado
2023-09-13  3:03 ` [PATCH v5 00/16] SME support for AArch64 gdb/gdbserver on Linux Thiago Jung Bauermann
2023-09-13 10:20   ` Luis Machado [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=49c3c4f2-b4e2-a127-f231-741247cb6166@arm.com \
    --to=luis.machado@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).