Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <airlied@gmail.com>, <simona@ffwll.ch>,
	<lucas.demarchi@intel.com>, <jani.nikula@linux.intel.com>,
	<christian.koenig@amd.com>, <alexander.deucher@amd.com>,
	<intel-xe@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	<himal.prasad.ghimiray@intel.com>,
	<aravind.iddamsetty@linux.intel.com>, <anshuman.gupta@intel.com>,
	<andriy.shevchenko@linux.intel.com>, <lina@asahilina.net>,
	<michal.wajdeczko@intel.com>, <andrealmeid@igalia.com>,
	 <amd-gfx@lists.freedesktop.org>, <kernel-dev@igalia.com>,
	<xaver.hugl@kde.org>, <pekka.paalanen@haloniitty.fi>
Subject: Re: [PATCH v12 3/5] drm/xe: Use device wedged event
Date: Tue, 4 Feb 2025 12:23:34 -0500	[thread overview]
Message-ID: <Z6JNFk5FiNtDIoiu@intel.com> (raw)
In-Reply-To: <20250204070528.1919158-4-raag.jadav@intel.com>

On Tue, Feb 04, 2025 at 12:35:26PM +0530, Raag Jadav wrote:
> This was previously attempted as xe specific reset uevent but dropped
> in commit 77a0d4d1cea2 ("drm/xe/uapi: Remove reset uevent for now")
> as part of refactoring.
> 
> Now that we have device wedged event provided by DRM core, make use
> of it and support both driver rebind and bus-reset based recovery.
> With this in place userspace will be notified of wedged device, on
> the basis of which, userspace may take respective action to recover
> the device.
> 
> $ udevadm monitor --property --kernel
> monitor will print the received events for:
> KERNEL - the kernel uevent
> 
> KERNEL[265.802982] change   /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:01.0/0000:03:00.0/drm/card0 (drm)
> ACTION=change
> DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:01.0/0000:03:00.0/drm/card0
> SUBSYSTEM=drm
> WEDGED=rebind,bus-reset
> DEVNAME=/dev/dri/card0
> DEVTYPE=drm_minor
> SEQNUM=5208
> MAJOR=226
> MINOR=0
> 
> v2: Change authorship to Himal (Aravind)
>     Add uevent for all device wedged cases (Aravind)
> v3: Generic implementation in DRM subsystem (Lucas)
> v4: Change authorship to Raag (Aravind)
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> Reviewed-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>


Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

to merge this through drm-misc-next

> ---
>  drivers/gpu/drm/xe/xe_device.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index f30f8f668dee..1cacefcb5afe 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -1120,7 +1120,8 @@ static void xe_device_wedged_fini(struct drm_device *drm, void *arg)
>   * re-probe (unbind + bind).
>   * In this state every IOCTL will be blocked so the GT cannot be used.
>   * In general it will be called upon any critical error such as gt reset
> - * failure or guc loading failure.
> + * failure or guc loading failure. Userspace will be notified of this state
> + * through device wedged uevent.
>   * If xe.wedged module parameter is set to 2, this function will be called
>   * on every single execution timeout (a.k.a. GPU hang) right after devcoredump
>   * snapshot capture. In this mode, GT reset won't be attempted so the state of
> @@ -1150,6 +1151,10 @@ void xe_device_declare_wedged(struct xe_device *xe)
>  			"IOCTLs and executions are blocked. Only a rebind may clear the failure\n"
>  			"Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n",
>  			dev_name(xe->drm.dev));
> +
> +		/* Notify userspace of wedged device */
> +		drm_dev_wedged_event(&xe->drm,
> +				     DRM_WEDGE_RECOVERY_REBIND | DRM_WEDGE_RECOVERY_BUS_RESET);
>  	}
>  
>  	for_each_gt(gt, xe, id)
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-02-04 17:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04  7:05 [PATCH v12 0/5] Introduce DRM device wedged event Raag Jadav
2025-02-04  7:05 ` [PATCH v12 1/5] drm: Introduce " Raag Jadav
2025-02-04 15:50   ` Christian König
2025-02-04  7:05 ` [PATCH v12 2/5] drm/doc: Document " Raag Jadav
2025-02-04  7:05 ` [PATCH v12 3/5] drm/xe: Use " Raag Jadav
2025-02-04 17:23   ` Rodrigo Vivi [this message]
2025-02-04  7:05 ` [PATCH v12 4/5] drm/i915: " Raag Jadav
2025-02-04 17:24   ` Rodrigo Vivi
2025-02-04 17:40     ` Tvrtko Ursulin
2025-02-04  7:05 ` [PATCH v12 5/5] drm/amdgpu: " Raag Jadav
2025-02-04  7:13 ` ✓ CI.Patch_applied: success for Introduce DRM device wedged event (rev10) Patchwork
2025-02-04  7:14 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-04  7:15 ` ✓ CI.KUnit: success " Patchwork
2025-02-04  7:31 ` ✓ CI.Build: " Patchwork
2025-02-04  7:34 ` ✓ CI.Hooks: " Patchwork
2025-02-04  7:35 ` ✗ CI.checksparse: warning " Patchwork
2025-02-04  7:56 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-04  8:55 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-12  6:57 ` [PATCH v12 0/5] Introduce DRM device wedged event Raag Jadav
2025-02-12 18:25   ` Rodrigo Vivi
2025-02-13 17:16     ` Rodrigo Vivi

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=Z6JNFk5FiNtDIoiu@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrealmeid@igalia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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=kernel-dev@igalia.com \
    --cc=lina@asahilina.net \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=pekka.paalanen@haloniitty.fi \
    --cc=raag.jadav@intel.com \
    --cc=simona@ffwll.ch \
    --cc=xaver.hugl@kde.org \
    /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