Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Simona Vetter <simona.vetter@ffwll.ch>
Cc: 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,
	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
Subject: Re: [PATCH v6 1/4] drm: Introduce device wedged event
Date: Wed, 25 Sep 2024 06:04:43 +0300	[thread overview]
Message-ID: <ZvN9yw5AYtxudNne@black.fi.intel.com> (raw)
In-Reply-To: <ZvKhIQGnGrcPURhD@phenom.ffwll.local>

On Tue, Sep 24, 2024 at 01:23:13PM +0200, Simona Vetter wrote:
> On Mon, Sep 23, 2024 at 09:28:23AM +0530, Raag Jadav wrote:
> > 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 no longer operating as
> > expected and has become unrecoverable from driver context.
> > 
> > Purpose of this implementation is to provide drivers a way to recover
> > through userspace intervention. Different drivers may have different
> > ideas of a "wedged device" depending on their hardware implementation,
> > and hence the vendor agnostic nature of the event. It is up to the drivers
> > to decide when they see the need for recovery and how they want to recover
> > from the available methods.
> > 
> > Current implementation defines three recovery methods, out of which,
> > drivers can choose to support any one or multiple of them. Preferred
> > recovery method will be sent in the uevent environment as WEDGED=<method>.
> > Userspace consumers (sysadmin) can define udev rules to parse this event
> > and take respective action to recover the device.
> > 
> >  Method    | Consumer expectations
> > -----------|-----------------------------------
> >  rebind    | unbind + rebind driver
> >  bus-reset | unbind + reset bus device + rebind
> >  reboot    | reboot system
> > 
> > v4: s/drm_dev_wedged/drm_dev_wedged_event
> >     Use drm_info() (Jani)
> >     Kernel doc adjustment (Aravind)
> > v5: Send recovery method with uevent (Lina)
> > v6: Access wedge_recovery_opts[] using helper function (Jani)
> >     Use snprintf() (Jani)
> > 
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> 
> Finally caught up on mail, so dropping this here again: Please also add a
> small section to drm-uapi.rst, pointing at these functions. Just the
> kerneldoc for developers is kinda not enough I think.

Would you prefer a new section or have the existing one (Device reset which
looks somewhat similar but not entirely) modified?

Raag

  reply	other threads:[~2024-09-25  3:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  3:58 [PATCH v6 0/4] Introduce DRM device wedged event Raag Jadav
2024-09-23  3:58 ` [PATCH v6 1/4] drm: Introduce " Raag Jadav
2024-09-23  8:38   ` Andy Shevchenko
2024-09-23 14:35     ` Raag Jadav
2024-09-23 14:57       ` Andy Shevchenko
2024-09-23 22:01         ` Jani Nikula
2024-09-24 11:23   ` Simona Vetter
2024-09-25  3:04     ` Raag Jadav [this message]
2024-09-25 11:53       ` Simona Vetter
2024-09-23  3:58 ` [PATCH v6 2/4] drm: Expose wedge recovery methods Raag Jadav
2024-09-23  3:58 ` [PATCH v6 3/4] drm/xe: Use device wedged event Raag Jadav
2024-09-23  3:58 ` [PATCH v6 4/4] drm/i915: " Raag Jadav
2024-09-25 15:44 ` ✗ CI.Patch_applied: failure for Introduce DRM device wedged event (rev4) Patchwork
2024-09-25 16:01 ` ✓ CI.Patch_applied: success " Patchwork
2024-09-25 16:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-25 16:05 ` ✓ CI.KUnit: success " Patchwork
2024-09-25 16:07 ` ✗ CI.Build: failure " Patchwork
2024-09-25 17:49 ` ✓ CI.Patch_applied: success " Patchwork
2024-09-25 17:49 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-25 17:51 ` ✓ CI.KUnit: success " Patchwork
2024-09-25 18:02 ` ✓ CI.Build: " Patchwork
2024-09-25 18:04 ` ✓ CI.Hooks: " Patchwork
2024-09-25 18:06 ` ✗ CI.checksparse: warning " Patchwork
2024-09-25 18:30 ` ✗ CI.BAT: failure " Patchwork
2024-09-25 20:07 ` ✗ CI.FULL: " 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=ZvN9yw5AYtxudNne@black.fi.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.vetter@ffwll.ch \
    --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