From: "Christian König" <christian.koenig@amd.com>
To: "Somalapuram, Amaranath" <asomalap@amd.com>,
"Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Sharma, Shashank" <Shashank.Sharma@amd.com>
Subject: Re: [PATCH 2/2] drm/amdgpu: add AMDGPURESET uevent on AMD GPU reset
Date: Mon, 17 Jan 2022 11:37:58 +0100 [thread overview]
Message-ID: <10fe91c4-9078-8937-5dac-0625d38c2ea3@amd.com> (raw)
In-Reply-To: <779d4778-6b85-2769-f169-f5f9e956a671@amd.com>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Am 17.01.22 um 11:34 schrieb Somalapuram, Amaranath:
> [SNIP]
> 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.
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.
Regards,
Christian.
> Regards,
>
> S.Amarnath
>
[-- Attachment #2: Type: text/html, Size: 1023 bytes --]
next prev parent reply other threads:[~2022-01-17 10:38 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 [this message]
2022-01-17 11:43 ` Sharma, Shashank
2022-01-17 11:57 ` Christian König
2022-01-17 14:19 ` Somalapuram, Amaranath
2022-01-17 16:07 ` Christian König
2022-01-17 11:54 ` Lazar, Lijo
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=10fe91c4-9078-8937-5dac-0625d38c2ea3@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Amaranath.Somalapuram@amd.com \
--cc=Shashank.Sharma@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=asomalap@amd.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 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.