From: Rob Clark <robdclark@gmail.com>
To: Shashank Sharma <contactshashanksharma@gmail.com>
Cc: Rob Clark <robdclark@chromium.org>,
Shashank Sharma <shashank.sharma@amd.com>,
Amaranath Somalapuram <amaranath.somalapuram@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Alexandar Deucher <alexander.deucher@amd.com>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH v2 1/2] drm: Add GPU reset sysfs event
Date: Wed, 16 Mar 2022 14:50:28 -0700 [thread overview]
Message-ID: <CAF6AEGtnXvo=-fKbgSRtAtZ80igqJM2bTKefiLPUsSohU9idNQ@mail.gmail.com> (raw)
In-Reply-To: <20220308180403.75566-1-contactshashanksharma@gmail.com>
On Tue, Mar 8, 2022 at 11:40 PM Shashank Sharma
<contactshashanksharma@gmail.com> wrote:
>
> From: Shashank Sharma <shashank.sharma@amd.com>
>
> This patch adds a new sysfs event, which will indicate
> the userland about a GPU reset, and can also provide
> some information like:
> - process ID of the process involved with the GPU reset
> - process name of the involved process
> - the GPU status info (using flags)
>
> This patch also introduces the first flag of the flags
> bitmap, which can be appended as and when required.
>
> V2: Addressed review comments from Christian and Amar
> - move the reset information structure to DRM layer
> - drop _ctx from struct name
> - make pid 32 bit(than 64)
> - set flag when VRAM invalid (than valid)
> - add process name as well (Amar)
>
> Cc: Alexandar Deucher <alexander.deucher@amd.com>
> Cc: Christian Koenig <christian.koenig@amd.com>
> Cc: Amaranath Somalapuram <amaranath.somalapuram@amd.com>
> Signed-off-by: Shashank Sharma <shashank.sharma@amd.com>
> ---
> drivers/gpu/drm/drm_sysfs.c | 31 +++++++++++++++++++++++++++++++
> include/drm/drm_sysfs.h | 10 ++++++++++
> 2 files changed, 41 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_sysfs.c b/drivers/gpu/drm/drm_sysfs.c
> index 430e00b16eec..840994810910 100644
> --- a/drivers/gpu/drm/drm_sysfs.c
> +++ b/drivers/gpu/drm/drm_sysfs.c
> @@ -409,6 +409,37 @@ void drm_sysfs_hotplug_event(struct drm_device *dev)
> }
> EXPORT_SYMBOL(drm_sysfs_hotplug_event);
>
> +/**
> + * drm_sysfs_reset_event - generate a DRM uevent to indicate GPU reset
> + * @dev: DRM device
> + * @reset_info: The contextual information about the reset (like PID, flags)
> + *
> + * Send a uevent for the DRM device specified by @dev. This informs
> + * user that a GPU reset has occurred, so that an interested client
> + * can take any recovery or profiling measure.
> + */
> +void drm_sysfs_reset_event(struct drm_device *dev, struct drm_reset_event *reset_info)
> +{
> + unsigned char pid_str[13];
> + unsigned char flags_str[15];
> + unsigned char pname_str[TASK_COMM_LEN + 6];
> + unsigned char reset_str[] = "RESET=1";
> + char *envp[] = { reset_str, pid_str, pname_str, flags_str, NULL };
> +
> + if (!reset_info) {
> + DRM_WARN("No reset info, not sending the event\n");
> + return;
> + }
> +
> + DRM_DEBUG("generating reset event\n");
> +
> + snprintf(pid_str, ARRAY_SIZE(pid_str), "PID=%u", reset_info->pid);
> + snprintf(pname_str, ARRAY_SIZE(pname_str), "NAME=%s", reset_info->pname);
> + snprintf(flags_str, ARRAY_SIZE(flags_str), "FLAGS=%u", reset_info->flags);
> + kobject_uevent_env(&dev->primary->kdev->kobj, KOBJ_CHANGE, envp);
> +}
> +EXPORT_SYMBOL(drm_sysfs_reset_event);
> +
> /**
> * drm_sysfs_connector_hotplug_event - generate a DRM uevent for any connector
> * change
> diff --git a/include/drm/drm_sysfs.h b/include/drm/drm_sysfs.h
> index 6273cac44e47..5ba11c760619 100644
> --- a/include/drm/drm_sysfs.h
> +++ b/include/drm/drm_sysfs.h
> @@ -1,16 +1,26 @@
> /* SPDX-License-Identifier: GPL-2.0 */
> #ifndef _DRM_SYSFS_H_
> #define _DRM_SYSFS_H_
> +#include <linux/sched.h>
> +
> +#define DRM_GPU_RESET_FLAG_VRAM_INVALID (1 << 0)
>
> struct drm_device;
> struct device;
> struct drm_connector;
> struct drm_property;
>
> +struct drm_reset_event {
> + uint32_t pid;
One side note, unrelated to devcoredump vs this..
AFAIU you probably want to be passing around a `struct pid *`, and
then somehow use pid_vnr() in the context of the process reading the
event to get the numeric pid. Otherwise things will not do what you
expect if the process triggering the crash is in a different pid
namespace from the compositor.
BR,
-R
> + uint32_t flags;
> + char pname[TASK_COMM_LEN];
> +};
> +
> int drm_class_device_register(struct device *dev);
> void drm_class_device_unregister(struct device *dev);
>
> void drm_sysfs_hotplug_event(struct drm_device *dev);
> +void drm_sysfs_reset_event(struct drm_device *dev, struct drm_reset_event *reset_info);
> void drm_sysfs_connector_hotplug_event(struct drm_connector *connector);
> void drm_sysfs_connector_status_event(struct drm_connector *connector,
> struct drm_property *property);
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-03-16 21:49 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:04 [PATCH v2 1/2] drm: Add GPU reset sysfs event Shashank Sharma
2022-03-08 18:04 ` [PATCH v2 2/2] drm/amdgpu: add work function for GPU reset event Shashank Sharma
2022-03-09 7:47 ` [PATCH v2 1/2] drm: Add GPU reset sysfs event Simon Ser
2022-03-09 11:18 ` Sharma, Shashank
2022-03-09 8:09 ` Christian König
2022-03-09 9:56 ` Pierre-Eric Pelloux-Prayer
2022-03-09 10:10 ` Simon Ser
2022-03-09 10:24 ` Christian König
2022-03-09 10:28 ` Simon Ser
2022-03-09 10:28 ` Pierre-Eric Pelloux-Prayer
2022-03-09 18:12 ` Rob Clark
2022-03-10 9:55 ` Christian König
2022-03-10 15:24 ` Rob Clark
2022-03-10 16:21 ` Sharma, Shashank
2022-03-10 16:27 ` Andrey Grodzovsky
2022-03-10 17:16 ` Rob Clark
2022-03-10 17:10 ` Rob Clark
2022-03-10 17:19 ` Sharma, Shashank
2022-03-10 17:40 ` Rob Clark
2022-03-10 18:33 ` Abhinav Kumar
2022-03-10 19:14 ` Sharma, Shashank
2022-03-10 19:35 ` Rob Clark
2022-03-10 19:44 ` Sharma, Shashank
2022-03-10 19:56 ` Rob Clark
2022-03-10 20:17 ` Sharma, Shashank
2022-03-11 8:30 ` Pekka Paalanen
2022-03-14 14:23 ` Alex Deucher
2022-03-14 15:26 ` Pekka Paalanen
2022-03-15 14:54 ` Alex Deucher
2022-03-16 8:48 ` Pekka Paalanen
2022-03-16 14:12 ` Alex Deucher
2022-03-16 15:36 ` Rob Clark
2022-03-16 15:48 ` Alex Deucher
2022-03-16 16:30 ` Rob Clark
2022-03-17 7:03 ` Christian König
2022-03-17 9:29 ` Daniel Vetter
2022-03-17 9:46 ` Christian König
2022-03-17 15:34 ` Rob Clark
2022-03-17 17:23 ` Daniel Vetter
2022-03-17 15:40 ` Rob Clark
2022-03-17 17:26 ` Daniel Vetter
2022-03-17 17:31 ` Rob Clark
2022-03-18 7:42 ` Christian König
2022-03-18 15:12 ` Rob Clark
2022-03-21 9:30 ` Christian König
2022-03-21 16:03 ` Rob Clark
2022-03-23 14:07 ` Daniel Stone
2022-03-23 15:14 ` Daniel Vetter
2022-03-23 15:25 ` Christian König
2022-03-26 0:53 ` Olsak, Marek
2022-03-29 12:14 ` Christian König
2022-03-29 16:25 ` Marek Olšák
2022-03-30 9:49 ` Daniel Vetter
2022-03-23 17:30 ` Rob Clark
2022-03-21 14:15 ` Daniel Vetter
2022-03-15 7:13 ` Dave Airlie
2022-03-15 7:25 ` Simon Ser
2022-03-15 7:25 ` Christian König
2022-03-17 9:25 ` Daniel Vetter
2022-03-16 21:50 ` Rob Clark [this message]
2022-03-17 8:42 ` Sharma, Shashank
2022-03-17 9:21 ` Christian König
2022-03-17 10:31 ` Daniel Stone
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='CAF6AEGtnXvo=-fKbgSRtAtZ80igqJM2bTKefiLPUsSohU9idNQ@mail.gmail.com' \
--to=robdclark@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amaranath.somalapuram@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=contactshashanksharma@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@chromium.org \
--cc=shashank.sharma@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 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 NNTP newsgroup(s).