Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: airlied@gmail.com, simona@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, lina@asahilina.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, andi.shyti@linux.intel.com,
	andriy.shevchenko@linux.intel.com, matthew.d.roper@intel.com,
	Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v5 0/4] Introduce DRM device wedged event
Date: Tue, 17 Sep 2024 09:32:31 +0530	[thread overview]
Message-ID: <20240917040235.197019-1-raag.jadav@intel.com> (raw)

This series introduces device wedged event in DRM subsystem and uses
it in xe and i915 drivers. Detailed description in commit message.

This was earlier attempted as xe specific uevent in v1 and v2.
https://patchwork.freedesktop.org/series/136909/

v2: Change authorship to Himal (Aravind)
    Add uevent for all device wedged cases (Aravind)
v3: Generic re-implementation in DRM subsystem (Lucas)
v4: s/drm_dev_wedged/drm_dev_wedged_event
    Use drm_info() (Jani)
    Kernel doc adjustment (Aravind)
    Change authorship to Raag (Aravind)
v5: Send recovery method with uevent (Lina)
    Expose supported recovery methods via sysfs (Lucas)

Raag Jadav (4):
  drm: Introduce device wedged event
  drm: Expose wedge recovery methods
  drm/xe: Use device wedged event
  drm/i915: Use device wedged event

 drivers/gpu/drm/drm_drv.c             | 37 +++++++++++++++++++++++++++
 drivers/gpu/drm/drm_sysfs.c           | 23 +++++++++++++++++
 drivers/gpu/drm/i915/gt/intel_reset.c |  2 ++
 drivers/gpu/drm/i915/i915_driver.c    | 10 ++++++++
 drivers/gpu/drm/xe/xe_device.c        | 17 ++++++++++--
 drivers/gpu/drm/xe/xe_device.h        |  1 +
 drivers/gpu/drm/xe/xe_pci.c           |  2 ++
 include/drm/drm_device.h              | 24 +++++++++++++++++
 include/drm/drm_drv.h                 |  1 +
 9 files changed, 115 insertions(+), 2 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-09-17  4:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  4:02 Raag Jadav [this message]
2024-09-17  4:02 ` [PATCH v5 1/4] drm: Introduce device wedged event Raag Jadav
2024-09-19  7:43   ` Jani Nikula
2024-09-17  4:02 ` [PATCH v5 2/4] drm: Expose wedge recovery methods Raag Jadav
2024-09-17  7:49   ` Jani Nikula
2024-09-19  4:05     ` Raag Jadav
2024-09-19  7:38       ` Jani Nikula
2024-09-19  8:38         ` Raag Jadav
2024-09-19  9:24           ` Jani Nikula
2024-09-19 11:33             ` Raag Jadav
2024-09-19 11:39               ` Jani Nikula
2024-09-19 13:45           ` Andy Shevchenko
2024-09-20 11:18             ` Raag Jadav
2024-09-20 14:27               ` Andy Shevchenko
2024-09-17  4:02 ` [PATCH v5 3/4] drm/xe: Use device wedged event Raag Jadav
2024-09-17  4:41   ` Ghimiray, Himal Prasad
2024-09-17  6:38     ` Raag Jadav
2024-09-17  8:03       ` Ghimiray, Himal Prasad
2024-09-17  8:18         ` Aravind Iddamsetty
2024-09-17  4:02 ` [PATCH v5 4/4] drm/i915: " Raag Jadav
2024-09-17  4:53 ` ✗ Fi.CI.CHECKPATCH: warning for Introduce DRM device wedged event (rev3) Patchwork
2024-09-17  4:53 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-17  5:13 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-17 12:23 ` ✓ Fi.CI.IGT: " 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=20240917040235.197019-1-raag.jadav@intel.com \
    --to=raag.jadav@intel.com \
    --cc=airlied@gmail.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --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=lina@asahilina.net \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --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