All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
	lucas.demarchi@intel.com, aravind.iddamsetty@linux.intel.com,
	umesh.nerlige.ramappa@intel.com, frank.scarbrough@intel.com,
	sk.anirban@intel.com, simona.vetter@ffwll.ch
Subject: Re: [PATCH v6 6/9] drm/xe/doc: Document device wedged and runtime survivability
Date: Fri, 25 Jul 2025 08:50:08 +0300	[thread overview]
Message-ID: <aIMbEPlNhNjskITi@black.fi.intel.com> (raw)
In-Reply-To: <20250724143440.232862-7-riana.tauro@intel.com>

On Thu, Jul 24, 2025 at 08:04:35PM +0530, Riana Tauro wrote:
> Add documentation for vendor specific device wedged recovery method
> and runtime survivability.

...

>  /**
> + * DOC: Xe Device Wedging
> + *
> + * Xe driver uses drm device wedged uevent as documented in Documentation/gpu/drm-uapi.rst.
> + *
> + * When device is in wedged state, every IOCTL will be blocked and GT cannot be
> + * used. Certain critical errors like gt reset failure, firmware failures can cause
> + * the device to be wedged. The default recovery method for a wedged state
> + * is rebind/bus-reset.
> + *
> + * Another recovery method is vendor-specific. Below are the usecases that trigger
> + * vendor-specific drm device wedged uevent and the procedure to be performed
> + * to recover the device.
> + *
> + * Case 1: CSC firmware errors require a firmware flash to restore normal device
> + *         operation. Since firmware flash is a vendor-specific action
> + *         ``WEDGED=vendor-specific`` recovery method along with
> + *         :ref:`runtime survivability mode <xe-survivability-mode>` is used to
> + *         notify userspace. User can then initiate a firmware flash using userspace tools
> + *         like fwupd to restore device to normal situation.

s/situation/operation

Reviewed-by: Raag Jadav <raag.jadav@intel.com>

  parent reply	other threads:[~2025-07-25  5:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 14:34 [PATCH v6 0/9] Handle Firmware reported Hardware Errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 1/9] drm: Add a vendor-specific recovery method to drm device wedged uevent Riana Tauro
2025-07-24 16:18   ` Rodrigo Vivi
2025-07-25  5:22     ` Riana Tauro
2025-07-25  5:22   ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 2/9] drm/xe: Set GT as wedged before sending " Riana Tauro
2025-07-24 14:34 ` [PATCH v6 3/9] drm/xe: Add a helper function to set recovery method Riana Tauro
2025-07-25  5:34   ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 4/9] drm/xe/xe_survivability: Refactor survivability mode Riana Tauro
2025-07-25  5:42   ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 5/9] drm/xe/xe_survivability: Add support for Runtime " Riana Tauro
2025-07-25  5:44   ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 6/9] drm/xe/doc: Document device wedged and runtime survivability Riana Tauro
2025-07-24 16:20   ` Rodrigo Vivi
2025-07-25  5:50   ` Raag Jadav [this message]
2025-07-24 14:34 ` [PATCH v6 7/9] drm/xe: Add support to handle hardware errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 8/9] drm/xe/xe_hw_error: Handle CSC Firmware reported Hardware errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 9/9] drm/xe/xe_hw_error: Add fault injection to trigger csc error handler Riana Tauro
2025-07-25 10:33   ` Raag Jadav
2025-07-24 14:39 ` ✗ CI.checkpatch: warning for Handle Firmware reported Hardware Errors (rev6) Patchwork
2025-07-24 14:40 ` ✓ CI.KUnit: success " Patchwork
2025-07-24 14:55 ` ✗ CI.checksparse: warning " Patchwork
2025-07-24 15:20 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-24 17:36 ` ✗ Xe.CI.Full: 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=aIMbEPlNhNjskITi@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frank.scarbrough@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=sk.anirban@intel.com \
    --cc=umesh.nerlige.ramappa@intel.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.