public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Raag Jadav <raag.jadav@intel.com>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: airlied@gmail.com, simona@ffwll.ch, mripard@kernel.org,
	matthew.brost@intel.com, rodrigo.vivi@intel.com,
	riana.tauro@intel.com, andrealmeid@igalia.com
Subject: Re: [PATCH v2 0/3] Update 'none' recovery method for DRM wedged event
Date: Mon, 23 Mar 2026 15:11:58 +0100	[thread overview]
Message-ID: <5d2171ca-aa9b-4b8f-9ea3-eabb823ef2d6@amd.com> (raw)
In-Reply-To: <acFJuRlHeJ8OyLi6@black.igk.intel.com>

On 3/23/26 15:10, Raag Jadav wrote:
> On Tue, Mar 10, 2026 at 08:56:58AM +0100, Raag Jadav wrote:
>> On Thu, Mar 05, 2026 at 06:36:46PM +0530, Raag Jadav wrote:
>>> Currently 'none' recovery method for wedged event expects no explicit
>>> recovery from userspace consumer but it expects driver to have reset
>>> the device, which may not always be the case. Update documentation and
>>> log to reflect this expectation.
>>
>> Anything I can do to move this forward?

Invent some tech to clone certain people so that we have more reviewers.

> Ping.

I will take a look now.

Christian.

> 
> Raag
> 
>>> v2: Rephrase documentation (Rodrigo)
>>>
>>> Raag Jadav (3):
>>>   drm/doc: Update documentation for 'none' recovery method
>>>   drm: Update log for 'none' recovery method
>>>   drm/xe: Send 'none' recovery method for
>>>     XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET
>>>
>>>  Documentation/gpu/drm-uapi.rst | 14 +++++++-------
>>>  drivers/gpu/drm/drm_drv.c      |  2 +-
>>>  drivers/gpu/drm/xe/xe_device.c |  9 ++++++++-
>>>  3 files changed, 16 insertions(+), 9 deletions(-)
>>>
>>> -- 
>>> 2.43.0
>>>


  reply	other threads:[~2026-03-23 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 13:06 [PATCH v2 0/3] Update 'none' recovery method for DRM wedged event Raag Jadav
2026-03-05 13:06 ` [PATCH v2 1/3] drm/doc: Update documentation for 'none' recovery method Raag Jadav
2026-03-05 14:16   ` Rodrigo Vivi
2026-03-23 14:13   ` Christian König
2026-03-05 13:06 ` [PATCH v2 2/3] drm: Update log " Raag Jadav
2026-03-23 14:13   ` Christian König
2026-03-05 13:06 ` [PATCH v2 3/3] drm/xe: Send 'none' recovery method for XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET Raag Jadav
2026-03-23 14:16   ` Christian König
2026-03-06 13:39 ` ✓ CI.KUnit: success for Update 'none' recovery method for DRM wedged event (rev2) Patchwork
2026-03-06 14:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-07 15:31 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-23 17:19   ` Raag Jadav
2026-03-10  7:56 ` [PATCH v2 0/3] Update 'none' recovery method for DRM wedged event Raag Jadav
2026-03-23 14:10   ` Raag Jadav
2026-03-23 14:11     ` Christian König [this message]
2026-03-24  2:36       ` Raag Jadav
2026-03-24 13:52         ` Rodrigo Vivi
2026-03-24 14:04           ` Raag Jadav

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=5d2171ca-aa9b-4b8f-9ea3-eabb823ef2d6@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=andrealmeid@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=mripard@kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    /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