Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: airlied@gmail.com, daniel@ffwll.ch, lucas.demarchi@intel.com,
	thomas.hellstrom@linux.intel.com, rodrigo.vivi@intel.com,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	tursulin@ursulin.net
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, himal.prasad.ghimiray@intel.com,
	francois.dugast@intel.com, aravind.iddamsetty@linux.intel.com,
	anshuman.gupta@intel.com, bellekallu.rajkiran@intel.com,
	saikishore.konda@intel.com, Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v3 1/3] drm: Introduce device wedged event
Date: Mon,  2 Sep 2024 13:18:57 +0530	[thread overview]
Message-ID: <20240902074859.2992849-2-raag.jadav@intel.com> (raw)
In-Reply-To: <20240902074859.2992849-1-raag.jadav@intel.com>

Introduce device wedged event, which will notify userspace of wedged
(hanged/unusable) state of the DRM device through a uevent. This is
useful especially in cases where the device is in unrecoverable state
and requires userspace intervention for recovery.

Purpose of this implementation is to be vendor agnostic. Userspace
consumers (sysadmin) can define udev rules to parse this event and
take respective action to recover the device.

Consumer expectations:
----------------------
1) Unbind driver
2) Reset bus device
3) Re-bind driver

Signed-off-by: Raag Jadav <raag.jadav@intel.com>
---
 drivers/gpu/drm/drm_drv.c | 21 +++++++++++++++++++++
 include/drm/drm_drv.h     |  1 +
 2 files changed, 22 insertions(+)

diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index 93543071a500..dc55cc237d89 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -499,6 +499,27 @@ void drm_dev_unplug(struct drm_device *dev)
 }
 EXPORT_SYMBOL(drm_dev_unplug);
 
+/**
+ * drm_dev_wedged - declare DRM device as wedged
+ * @dev: DRM device
+ *
+ * This declares a DRM device specified by @dev as wedged (hanged/unusable)
+ * and generates a uevent for it, on the basis of which, userspace may take
+ * respective action to recover the device.
+ * Currently we only set WEDGED=1 in the uevent environment, but this can
+ * be expanded in the future.
+ */
+void drm_dev_wedged(struct drm_device *dev)
+{
+	char *event_string = "WEDGED=1";
+	char *envp[] = { event_string, NULL };
+
+	DRM_INFO("%s: device wedged, generating uevent\n", dev_name(dev->dev));
+
+	kobject_uevent_env(&dev->primary->kdev->kobj, KOBJ_CHANGE, envp);
+}
+EXPORT_SYMBOL(drm_dev_wedged);
+
 /*
  * DRM internal mount
  * We want to be able to allocate our own "struct address_space" to control
diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
index cd37936c3926..a0b2d1435b86 100644
--- a/include/drm/drm_drv.h
+++ b/include/drm/drm_drv.h
@@ -489,6 +489,7 @@ void drm_put_dev(struct drm_device *dev);
 bool drm_dev_enter(struct drm_device *dev, int *idx);
 void drm_dev_exit(int idx);
 void drm_dev_unplug(struct drm_device *dev);
+void drm_dev_wedged(struct drm_device *dev);
 
 /**
  * drm_dev_is_unplugged - is a DRM device unplugged
-- 
2.34.1


  reply	other threads:[~2024-09-02  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  7:48 [PATCH v3 0/3] Introduce DRM device wedged event Raag Jadav
2024-09-02  7:48 ` Raag Jadav [this message]
2024-09-02  7:51   ` [PATCH v3 1/3] drm: Introduce " Jani Nikula
2024-09-02  9:14   ` Aravind Iddamsetty
2024-09-03  7:48     ` Raag Jadav
2024-09-02  7:48 ` [PATCH v3 2/3] drm/xe: Use " Raag Jadav
2024-09-02  9:09   ` Aravind Iddamsetty
2024-09-02  7:48 ` [PATCH v3 3/3] drm/i915: " Raag Jadav
2024-09-02  8:52   ` Aravind Iddamsetty
2024-09-03  7:03     ` Raag Jadav
2024-09-02  8:33 ` ✗ Fi.CI.CHECKPATCH: warning for Introduce DRM " Patchwork
2024-09-02  8:33 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-02  8:39 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-02 11:27 ` ✗ Fi.CI.IGT: failure " Patchwork

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=20240902074859.2992849-2-raag.jadav@intel.com \
    --to=raag.jadav@intel.com \
    --cc=airlied@gmail.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=bellekallu.rajkiran@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francois.dugast@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=saikishore.konda@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    /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