public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 00/12] Initial support for ROCm platform (AMDGPU) debugging
Date: Thu, 5 Jan 2023 14:41:07 -0500	[thread overview]
Message-ID: <f2852a04-8430-5d45-2aea-5311e4dae81c@simark.ca> (raw)
In-Reply-To: <20221206135729.3937767-1-simon.marchi@efficios.com>

On 12/6/22 08:57, Simon Marchi via Gdb-patches wrote:
> This patch series adds initial support for debugging programs offloaded
> to AMD GPUs using the ROCm platform.
> 
> Patches 1 to 11 are preparatory patches, and patch 12 is the big one.
> We included in that patch only what we consider to be the bare minimum
> for a cohesive first step, something that can be run and tested.  See
> the commit message of patch 12 for more details.
> 
> At the end of this series, it is possible to hit breakpoints in GPU code
> and resume execution until the end of the program.  Notably, GDB is not
> able to compute the backtrace, which is of course an important piece to
> do any real debugging.  Supporting this will require GDB to support some
> extensions to DWARF, which is a big piece in itself.  This part, as well
> as other features, will come as future patches.
> 
> Patch 12 also contains documentation changes.  This series was tested on
> Ubuntu 22.04, and no regressions appear for x86-64 / Linux debugging
> when and the AMDGPU / ROCm platform support is compiled in.
> Built-tested with --enable-targets=all.
> 
> Porting GDB to the ROCm platform brought up many challenges and has a
> few interesting differences, compared to a "standard" CPU port.  We did
> a presentation at the 2022 Cauldron, in Prague, that explains some of
> them:
> 
>   https://www.youtube.com/watch?v=X1iZ_Ta7jOo

FYI, I pushed patches 5, 7, 8 and 9, since they seemed like good
changes, independently from this series (and they were LGTM'ed by
Andrew).

Simon

      parent reply	other threads:[~2023-01-05 19:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 13:57 Simon Marchi
2022-12-06 13:57 ` [PATCH 01/12] gdb: add supports_arch_info callback to gdbarch_register Simon Marchi
2022-12-06 16:45   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 02/12] gdb: make install_breakpoint return a non-owning reference Simon Marchi
2022-12-06 16:46   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 03/12] gdbsupport: add type definitions for pid, lwp and tid Simon Marchi
2022-12-06 16:36   ` Andrew Burgess
2022-12-07  2:55     ` Simon Marchi
2022-12-06 13:57 ` [PATCH 04/12] gdb: add inferior_pre_detach observable Simon Marchi
2022-12-06 16:39   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 05/12] gdb: make gdbarch_alloc take ownership of the tdep Simon Marchi
2022-12-06 17:06   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 06/12] gdb: add gdbarch_up Simon Marchi
2022-12-06 17:07   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 07/12] gdbsupport: move libxxhash configure check to gdbsupport Simon Marchi
2022-12-06 17:19   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 08/12] gdbsupport: move fast_hash to gdbsupport/common-utils.h Simon Marchi
2022-12-06 17:19   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 09/12] gdbsupport: add gdb::string_view_hash Simon Marchi
2022-12-06 17:19   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 10/12] gdb/solib-svr4: don't disable probes interface if probe not found Simon Marchi
2022-12-06 13:57 ` [PATCH 11/12] gdb: make gdb_printing_disassembler::stream public Simon Marchi
2022-12-06 17:38   ` Andrew Burgess
2022-12-06 13:57 ` [PATCH 12/12] gdb: initial support for ROCm platform (AMDGPU) debugging Simon Marchi
2022-12-06 15:00   ` Eli Zaretskii
2022-12-06 15:10     ` Simon Marchi
2022-12-06 15:42   ` Eli Zaretskii
2022-12-07  2:17     ` Simon Marchi
2022-12-07 13:29       ` Eli Zaretskii
2022-12-16 17:37         ` Simon Marchi
2023-01-05 19:41 ` Simon Marchi [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=f2852a04-8430-5d45-2aea-5311e4dae81c@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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).