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>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>
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 4/5] drm/i915: Use device wedged event
Date: Tue, 4 Feb 2025 12:24:36 -0500	[thread overview]
Message-ID: <Z6JNVF7O_Da8wA7p@intel.com> (raw)
In-Reply-To: <20250204070528.1919158-5-raag.jadav@intel.com>

On Tue, Feb 04, 2025 at 12:35:27PM +0530, Raag Jadav wrote:
> 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
> gt reset failure.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> Reviewed-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/gt/intel_reset.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c

Joonas, Tvrtko, ack on getting this through drm-misc-next?

> index aae5a081cb53..d6dc12fd87c1 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -1422,6 +1422,9 @@ static void intel_gt_reset_global(struct intel_gt *gt,
>  
>  	if (!test_bit(I915_WEDGED, &gt->reset.flags))
>  		kobject_uevent_env(kobj, KOBJ_CHANGE, reset_done_event);
> +	else
> +		drm_dev_wedged_event(&gt->i915->drm,
> +				     DRM_WEDGE_RECOVERY_REBIND | DRM_WEDGE_RECOVERY_BUS_RESET);
>  }
>  
>  /**
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-02-04 17:25 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
2025-02-04  7:05 ` [PATCH v12 4/5] drm/i915: " Raag Jadav
2025-02-04 17:24   ` Rodrigo Vivi [this message]
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=Z6JNVF7O_Da8wA7p@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=joonas.lahtinen@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=tursulin@ursulin.net \
    --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