From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simark@simark.ca>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] amdgpu: handle fork and exec
Date: Mon, 17 Apr 2023 13:57:34 -0400 [thread overview]
Message-ID: <3ad78643-be4b-d6fb-2b43-c80e0984edf4@polymtl.ca> (raw)
In-Reply-To: <bae2a0cc-0b78-357f-3f28-a6ebecf86132@simark.ca>
On 4/13/23 11:54, Simon Marchi wrote:
> On 4/3/23 14:52, Simon Marchi via Gdb-patches wrote:
>> 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.
>
> If there is no feedback on this (the non-amdgpu-specific bits may be
> relevant to review), I intend to push this next week.
>
> Simon
I just pushed this.
Simon
prev parent reply other threads:[~2023-04-17 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:52 Simon Marchi
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 [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=3ad78643-be4b-d6fb-2b43-c80e0984edf4@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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).