From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/7] amdgpu: handle fork and exec
Date: Mon, 3 Apr 2023 14:52:01 -0400 [thread overview]
Message-ID: <20230403185208.197965-1-simon.marchi@efficios.com> (raw)
This series adds support for fork and exec to the amdgpu port. This
means making sure that the appropriate cleanups are done when an
inferior using the GPU forks and / or execs, and the appropriates
actions taken so that we can properly debug an inferior using the GPU
post-fork or post-exec.
Simon Marchi (7):
gdb: pass execing and following inferior to inferior_execd observers
gdb: add inferior_forked observable
gdb: remove regcache::target
gdb: add maybe_switch_inferior function
gdb: make regcache::raw_update switch to right inferior
gdb: switch to right inferior in fetch_inferior_event
gdb/amdgpu: add follow fork and exec support
gdb/amd-dbgapi-target.c | 39 ++++++++
gdb/gdbthread.h | 2 +
gdb/inferior.c | 15 ++++
gdb/inferior.h | 7 ++
gdb/infrun.c | 53 ++++++-----
gdb/jit.c | 20 +++--
gdb/linux-tdep.c | 10 ++-
gdb/observable.c | 1 +
gdb/observable.h | 17 +++-
gdb/record-btrace.c | 3 +-
gdb/regcache.c | 90 ++++++++++++-------
gdb/regcache.h | 22 +++--
gdb/solib.c | 3 +-
.../fork-exec-gpu-to-non-gpu-execee.cpp | 27 ++++++
.../fork-exec-gpu-to-non-gpu-execer.cpp | 55 ++++++++++++
.../gdb.rocm/fork-exec-gpu-to-non-gpu.exp | 89 ++++++++++++++++++
.../fork-exec-non-gpu-to-gpu-execee.cpp | 36 ++++++++
.../fork-exec-non-gpu-to-gpu-execer.cpp | 46 ++++++++++
.../gdb.rocm/fork-exec-non-gpu-to-gpu.exp | 88 ++++++++++++++++++
gdb/thread.c | 14 +++
20 files changed, 561 insertions(+), 76 deletions(-)
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-gpu-to-non-gpu-execee.cpp
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-gpu-to-non-gpu-execer.cpp
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-gpu-to-non-gpu.exp
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-non-gpu-to-gpu-execee.cpp
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-non-gpu-to-gpu-execer.cpp
create mode 100644 gdb/testsuite/gdb.rocm/fork-exec-non-gpu-to-gpu.exp
--
2.40.0
next reply other threads:[~2023-04-03 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:52 Simon Marchi [this message]
2023-04-03 18:52 ` [PATCH 1/7] gdb: pass execing and following inferior to inferior_execd observers Simon Marchi
2023-04-03 18:52 ` [PATCH 2/7] gdb: add inferior_forked observable Simon Marchi
2023-04-03 18:52 ` [PATCH 3/7] gdb: remove regcache::target Simon Marchi
2023-04-03 18:52 ` [PATCH 4/7] gdb: add maybe_switch_inferior function Simon Marchi
2023-04-03 18:52 ` [PATCH 5/7] gdb: make regcache::raw_update switch to right inferior Simon Marchi
2023-04-03 18:52 ` [PATCH 6/7] gdb: switch to right inferior in fetch_inferior_event Simon Marchi
2023-04-03 18:52 ` [PATCH 7/7] gdb/amdgpu: add follow fork and exec support Simon Marchi
2023-04-13 15:54 ` [PATCH 0/7] amdgpu: handle fork and exec Simon Marchi
2023-04-17 17:57 ` Simon Marchi
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=20230403185208.197965-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.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).