public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>,
	Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 0/8] gdbserver improvements for AArch64 SVE support
Date: Tue, 7 May 2024 15:43:55 +0100	[thread overview]
Message-ID: <4d5ffba6-4f8c-418d-ad29-67b5b95c7bd9@arm.com> (raw)
In-Reply-To: <MN2PR11MB456622174F2B457AFD6F3A5D8EE42@MN2PR11MB4566.namprd11.prod.outlook.com>

Hi,

On 5/7/24 15:29, Willgerodt, Felix wrote:
>> -----Original Message-----
>> From: Gdb-patches <gdb-patches-
>> bounces+felix.willgerodt=intel.com@sourceware.org> On Behalf Of Thiago Jung
>> Bauermann via Gdb-patches
>> Sent: Montag, 30. Januar 2023 05:45
>> To: gdb-patches@sourceware.org
>> Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
>> Subject: [PATCH v3 0/8] gdbserver improvements for AArch64 SVE support
>>
>> Hello,
>>
>> This is version 3 of the patch series adding support to gdbserver for
>> inferiors that change the SVE vector length at runtime. This is already
>> supported by GDB, but not by gdbserver. Version 2 was posted here:
>>
>> https://inbox.sourceware.org/gdb-patches/20221126020452.1686509-1-
>> thiago.bauermann@linaro.org/
>>
>> This version incorporates the review comments from v2 (thanks!). The
>> biggest change is that it implements Simon's idea¹:
>>
>>> If it's the case, that we need to extend the RSP to allow fetching
>>> per-thread tdesc, here's the idea I had in mind for a while, to avoid
>>> adding too much overhead.  Stop replies and the qXfer:threads:read reply
>>> could include a per-thread tdesc identifier.  That tdesc identifier
>>> would be something short, either an incrementing number, or some kind of
>>> hash of the tdesc.  It would be something opaque chosen by the stub.  A
>>> new packet would be introduced to allow GDB to request the XML given
>>> that ID.  On the GDB side, GDB would request the XML when encountering a
>>> tdesc ID it doesn't know about, and then cache the result.
>>
>> The only difference from the above in this series is that instead of
>> creating a new packet to allow GDB to request the XML given the ID, I'm
>> extending the qXfer:features:read request: GDB can send "target-id-%u.xml"
>> as the annex, where %u is the target description ID. Please let me know if
>> you think a separate packet would be better. The remote protocol changes
>> are documented in patch 5.
>>
>> I had to drop the Reviewed-by tags from some patches because they have some
>> significant changes from the version that was reviewed.
>>
>> There's also a new testcase exercising the case of an inferior's thread
>> changing its SVE vector length. The previous version of this series failed
>> the testcase, but this one passes it.
>>
>> With this series applied, gdb.arch/aarch64-sve.exp passes all tests on
>> extended-remote aarch64-linux. Without them, it fails tests after the
>> testcase changes the vector length.
>>
>> Tested on native and extended-remote aarch64-linux, x86_64-linux and
>> armv7l-linux-gnueabihf (the last one on QEMU TCG).
>>
>> ¹ https://inbox.sourceware.org/gdb-patches/559069a3-f3ce-2059-bf4a-
>> 44add43979f7@simark.ca/
> 
> Hi Thiago, Hi Luis,
> 
> I wonder what happened to this series. Do you plan to revive it at some
> point? I realise this isn't an easy series to land. Tough it would be great
> to have in my view.

I think it is an essential piece to make gdbserver work correctly for both
SVE and SME (and similar features on other architectures), as well as enabling
remote debugging stubs to support vector size changes mid-execution.

Thiago was the last one to touch this code, so he may have better information on
future plans.

Unfortunately I don't have cycles to get back to this particular feature at the
moment, but I'd gladly review future iterations of the series.

> 
> Regards,
> Felix
> 
> 
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2024-05-07 14:44 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  4:45 Thiago Jung Bauermann
2023-01-30  4:45 ` [PATCH v3 1/8] gdbserver: Add assert in find_register_by_number Thiago Jung Bauermann
2023-01-31 17:05   ` Simon Marchi
2023-01-31 19:49     ` Thiago Jung Bauermann
2023-02-01 15:43       ` Simon Marchi
2023-01-30  4:45 ` [PATCH v3 2/8] gdbserver: Add PID parameter to linux_get_auxv and linux_get_hwcap Thiago Jung Bauermann
2023-02-01  9:07   ` Luis Machado
2023-02-01 10:54   ` Andrew Burgess
2023-02-01 16:01     ` Simon Marchi
2023-02-01 19:33       ` Thiago Jung Bauermann
2023-02-01 19:53         ` Simon Marchi
2023-02-01 21:55           ` Thiago Jung Bauermann
2023-02-06 19:54   ` Pedro Alves
2023-02-06 20:16     ` Simon Marchi
2023-02-07 15:19       ` Pedro Alves
2023-02-07 21:47         ` Thiago Jung Bauermann
2023-02-09  1:31           ` Simon Marchi
2023-02-10  3:54             ` Thiago Jung Bauermann
2023-02-07 22:28     ` Thiago Jung Bauermann
2023-01-30  4:45 ` [PATCH v3 3/8] gdbserver/linux-aarch64: Factor out function to get aarch64_features Thiago Jung Bauermann
2023-02-01  8:59   ` Luis Machado
2023-02-01 16:04     ` Simon Marchi
2023-02-01 22:13       ` Thiago Jung Bauermann
2023-01-30  4:45 ` [PATCH v3 4/8] gdbserver/linux-aarch64: When thread stops, update its target description Thiago Jung Bauermann
2023-02-01  9:05   ` Luis Machado
2023-02-01 11:06   ` Andrew Burgess
2023-02-01 16:21     ` Simon Marchi
2023-02-01 16:32       ` Luis Machado
2023-02-02  2:54         ` Thiago Jung Bauermann
2023-02-02  3:47           ` Simon Marchi
2023-02-03  3:47             ` Thiago Jung Bauermann
2023-02-03 11:13               ` Luis Machado
2023-02-04 15:26                 ` Thiago Jung Bauermann
2023-02-03 11:11             ` Luis Machado
2023-02-04 15:21               ` Thiago Jung Bauermann
2023-02-06  9:07                 ` Luis Machado
2023-02-06 12:15                   ` Thiago Jung Bauermann
2023-02-06 20:29                 ` Pedro Alves
2023-02-07  8:11                   ` Luis Machado
2023-02-07 14:39                     ` Thiago Jung Bauermann
2023-02-03 10:57           ` Luis Machado
2023-02-04  6:18             ` Thiago Jung Bauermann
2023-02-06 20:26           ` Pedro Alves
2023-02-07 21:06             ` Thiago Jung Bauermann
2023-02-09  2:46               ` Simon Marchi
2023-02-10  3:29                 ` Thiago Jung Bauermann
2023-02-10 14:56                   ` Luis Machado
2023-02-10 15:04                     ` Tom Tromey
2023-02-10 15:28                       ` Luis Machado
2023-02-10 17:26                       ` Thiago Jung Bauermann
2023-02-10 21:01                         ` Simon Marchi
2023-01-30  4:45 ` [PATCH v3 5/8] gdbserver: Transmit target description ID in thread list and stop reply Thiago Jung Bauermann
2023-01-30 12:52   ` Eli Zaretskii
2023-01-30 14:05     ` Thiago Jung Bauermann
2023-02-01  9:39   ` Luis Machado
2023-02-01 12:07   ` Andrew Burgess
2023-02-01 13:03     ` Eli Zaretskii
2023-02-01 17:37     ` Simon Marchi
2023-02-02 20:36       ` Thiago Jung Bauermann
2023-02-02 20:56         ` Simon Marchi
2023-02-01 20:46     ` Simon Marchi
2023-02-02 21:43       ` Thiago Jung Bauermann
2023-02-01 14:51   ` Andrew Burgess
2023-02-01 17:03     ` Simon Marchi
2023-02-02 19:52       ` Thiago Jung Bauermann
2023-02-02 20:51         ` Simon Marchi
2023-02-03  2:44           ` Thiago Jung Bauermann
2023-02-03 16:29             ` Andrew Burgess
2023-02-04  6:08               ` Thiago Jung Bauermann
2023-02-03 11:22       ` Luis Machado
2023-02-03 12:50         ` Simon Marchi
2023-01-30  4:45 ` [PATCH v3 6/8] gdb/remote: Parse tdesc field in stop reply and threads list XML Thiago Jung Bauermann
2023-02-01  9:52   ` Luis Machado
2023-02-05  0:06     ` Thiago Jung Bauermann
2023-02-06  9:10       ` Luis Machado
2023-02-01 14:32   ` Andrew Burgess
2023-02-01 19:50     ` Simon Marchi
2023-02-01 20:16       ` Simon Marchi
2023-02-03 11:27         ` Luis Machado
2023-02-03 13:19           ` Simon Marchi
2023-02-03 16:33             ` Andrew Burgess
2023-01-30  4:45 ` [PATCH v3 7/8] gdb/aarch64: Detect vector length changes when debugging remotely Thiago Jung Bauermann
2023-02-01  9:58   ` Luis Machado
2023-02-01 15:26   ` Andrew Burgess
2023-02-01 20:20     ` Simon Marchi
2023-02-03 11:31       ` Luis Machado
2023-02-03 16:38       ` Andrew Burgess
2023-02-03 19:07         ` Simon Marchi
2023-01-30  4:45 ` [PATCH v3 8/8] gdb/testsuite: Add test to exercise multi-threaded AArch64 SVE inferiors Thiago Jung Bauermann
2023-02-01 10:10   ` Luis Machado
2023-02-06 19:11 ` [PATCH v3 0/8] gdbserver improvements for AArch64 SVE support Pedro Alves
2023-02-06 20:05   ` Simon Marchi
2023-02-06 21:06     ` Pedro Alves
2023-02-07 13:49       ` Simon Marchi
2024-05-07 14:29 ` Willgerodt, Felix
2024-05-07 14:43   ` Luis Machado [this message]
2024-05-07 16:34     ` Thiago Jung Bauermann
2024-05-10 13:47       ` Willgerodt, Felix

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=4d5ffba6-4f8c-418d-ad29-67b5b95c7bd9@arm.com \
    --to=luis.machado@arm.com \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).