From: "Somalapuram, Amaranath" <firstname.lastname@example.org>
To: "Christian König" <email@example.com>,
"Sharma, Shashank" <firstname.lastname@example.org>,
"Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Subject: Re: [PATCH 2/2] drm/amdgpu: add AMDGPURESET uevent on AMD GPU reset
Date: Mon, 17 Jan 2022 19:49:33 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
if sending udev event during reset is going to create problem, we can
move this code from reset sequence to re-int (after GPU reset succeeded).
On 1/17/2022 5:27 PM, Christian König wrote:
> Am 17.01.22 um 12:43 schrieb Sharma, Shashank:
>> Hello Christian,
>> On 1/17/2022 11:37 AM, Christian König wrote:
>>> Am 17.01.22 um 11:34 schrieb Somalapuram, Amaranath:
>>>> Any suggestion how we can notify user space during this situation.
>>> Well trace points should work. They use a ring buffer and are
>>> specially made to work in such situations.
>> We are anyways sending a trace event with data, but can trace event
>> be a wake up source for an application (like a tracer) ? This DRM
>> event is just to indicate that reset happened, so app has to read
>> from trace file.
> Yeah, that's a really good question I can't fully answer. As far as I
> know you can filter in userspace what you get from the tracer, but I
> don't know if you can block on a specific event.
>>> Alternative would be to audit the udev code and allow giving a GFP
>>> mask to the function to make sure that we don't run into the deadlock.
>>> Another alternative is a debugfs file which just blocks for the next
>>> reset to happen.
>> - Shashank
next prev parent reply other threads:[~2022-01-17 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 6:33 [PATCH 2/2] drm/amdgpu: add AMDGPURESET uevent on AMD GPU reset Somalapuram Amaranath
2022-01-17 7:27 ` Christian König
2022-01-17 10:01 ` Somalapuram, Amaranath
2022-01-17 10:03 ` Christian König
2022-01-17 10:09 ` Somalapuram, Amaranath
2022-01-17 10:19 ` Christian König
2022-01-17 10:34 ` Somalapuram, Amaranath
2022-01-17 10:37 ` Christian König
2022-01-17 11:43 ` Sharma, Shashank
2022-01-17 11:57 ` Christian König
2022-01-17 14:19 ` Somalapuram, Amaranath [this message]
2022-01-17 16:07 ` Christian König
2022-01-17 11:54 ` Lazar, Lijo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.