From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
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>, <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 v5 3/4] drm/xe: Use device wedged event
Date: Tue, 17 Sep 2024 13:33:44 +0530 [thread overview]
Message-ID: <97077405-333d-4940-94e1-7e6a5d9c38b5@intel.com> (raw)
In-Reply-To: <Zukj9y2oZve73NLy@black.fi.intel.com>
On 17-09-2024 12:08, Raag Jadav wrote:
> On Tue, Sep 17, 2024 at 10:11:05AM +0530, Ghimiray, Himal Prasad wrote:
>> On 17-09-2024 09:32, 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 supported by DRM core, make use
>>> of it. 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.
>>
>>
>> As per earlier discussions, the UAPI was also supposed to provide the reason
>> for wedging( which is supposedly used by L0). IS that requirement nomore in
>> place ?
>
> Wondering how does that contribute to the usecase?
ZES_EVENT_TYPE_FLAG_DEVICE_RESET_REQUIRED uses zesDeviceGetState
"Get information about the state of the device - if a reset is required,
reasons for the reset and if the device has been repaired. "
https://spec.oneapi.io/level-zero/latest/sysman/api.html#zes__api_8h_1aec73230b938f08ad632d0b7817b66183
>
> Raag
next prev parent reply other threads:[~2024-09-17 8:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 4:02 [PATCH v5 0/4] Introduce DRM device wedged event Raag Jadav
2024-09-17 4:02 ` [PATCH v5 1/4] drm: Introduce " Raag Jadav
2024-09-19 7:43 ` Jani Nikula
2024-09-17 4:02 ` [PATCH v5 2/4] drm: Expose wedge recovery methods Raag Jadav
2024-09-17 7:49 ` Jani Nikula
2024-09-19 4:05 ` Raag Jadav
2024-09-19 7:38 ` Jani Nikula
2024-09-19 8:38 ` Raag Jadav
2024-09-19 9:24 ` Jani Nikula
2024-09-19 11:33 ` Raag Jadav
2024-09-19 11:39 ` Jani Nikula
2024-09-19 13:45 ` Andy Shevchenko
2024-09-20 11:18 ` Raag Jadav
2024-09-20 14:27 ` Andy Shevchenko
2024-09-17 4:02 ` [PATCH v5 3/4] drm/xe: Use device wedged event Raag Jadav
2024-09-17 4:41 ` Ghimiray, Himal Prasad
2024-09-17 6:38 ` Raag Jadav
2024-09-17 8:03 ` Ghimiray, Himal Prasad [this message]
2024-09-17 8:18 ` Aravind Iddamsetty
2024-09-17 4:02 ` [PATCH v5 4/4] drm/i915: " Raag Jadav
2024-09-17 4:53 ` ✗ Fi.CI.CHECKPATCH: warning for Introduce DRM device wedged event (rev3) Patchwork
2024-09-17 4:53 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-17 5:13 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-17 12:23 ` ✓ Fi.CI.IGT: " 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=97077405-333d-4940-94e1-7e6a5d9c38b5@intel.com \
--to=himal.prasad.ghimiray@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=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=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--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