From: Lancelot Six <lancelot.six@amd.com>
To: <gdb-patches@sourceware.org>
Cc: <lsix@lancelotsix.com>, Lancelot Six <lancelot.six@amd.com>
Subject: [PATCH 0/2] Fix debugging multi inferiors using the ROCm runtime
Date: Fri, 30 Jun 2023 14:57:53 +0000 [thread overview]
Message-ID: <20230630145755.6500-1-lancelot.six@amd.com> (raw)
Hi,
This series fixes an issue seen when debugging multiple inferiors which
use AMDGPU devices. This problem appears on systems using GPUs capable
of debugging multiple processes simultaneously.
The first patch adds a helper method for the testsuite which checks if
all devices on the system support multi-process debugging. The second
patch fixes the multi inferior issue and adds a testcase to exercise the
problem.
All feedbacks are welcome.
Best,
Lancelot.
Lancelot Six (2):
gdb/testsuite/rocm: Add the hip_devices_support_debug_multi_process
proc
gdb/amdgpu: Fix debugging multiple inferiors using the ROCm runtime
gdb/amd-dbgapi-target.c | 6 +-
gdb/testsuite/gdb.rocm/multi-inferior-gpu.cpp | 111 ++++++++++++++++++
gdb/testsuite/gdb.rocm/multi-inferior-gpu.exp | 86 ++++++++++++++
gdb/testsuite/lib/rocm.exp | 20 ++++
4 files changed, 221 insertions(+), 2 deletions(-)
create mode 100644 gdb/testsuite/gdb.rocm/multi-inferior-gpu.cpp
create mode 100644 gdb/testsuite/gdb.rocm/multi-inferior-gpu.exp
base-commit: 69933be89fe5002d2d541ecf2145d5ccac19bbac
--
2.34.1
next reply other threads:[~2023-06-30 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:57 Lancelot Six [this message]
2023-06-30 14:57 ` [PATCH 1/2] gdb/testsuite/rocm: Add the hip_devices_support_debug_multi_process proc Lancelot Six
2023-07-28 18:00 ` Pedro Alves
2023-06-30 14:57 ` [PATCH 2/2] gdb/amdgpu: Fix debugging multiple inferiors using the ROCm runtime Lancelot Six
2023-07-28 18:01 ` Pedro Alves
2023-07-28 18:04 ` Pedro Alves
2023-07-28 16:47 ` [PING] [PATCH 0/2] Fix debugging multi " Lancelot SIX
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=20230630145755.6500-1-lancelot.six@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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).