From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>,
<intel-xe@lists.freedesktop.org>, <rodrigo.vivi@intel.com>,
<matthew.brost@intel.com>, <thomas.hellstrom@linux.intel.com>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<vinay.belgaumkar@intel.com>, <aravind.iddamsetty@intel.com>,
<karthik.poosa@intel.com>, <sk.anirban@intel.com>,
<raag.jadav@intel.com>
Subject: Re: [RFC PATCH v4 3/5] drm/xe: use xe_ras_log_wedged macro in xe_device_declare_wedged
Date: Tue, 7 Jul 2026 05:27:40 +0530 [thread overview]
Message-ID: <21c1df90-0862-4056-ae65-4bcbce1640ef@intel.com> (raw)
In-Reply-To: <3684bbf3-e4c4-48f6-8f31-fcbd3f29e848@intel.com>
On 06-07-2026 02:06 pm, Tauro, Riana wrote:
>
> On 30-06-2026 17:25, Mallesh Koujalagi wrote:
>> Replace the open-coded drm_err() call with xe_ras_log_wedged()
>> macro so that wedge events are reported through the unified
>> RAS/SIG logging path with a consistent format, CPER severity,
>> and errno.
>>
>> Signed-off-by: Mallesh Koujalagi<mallesh.koujalagi@intel.com>
>> ---
>> v2:
>> - Rebase.
>>
>> v3:
>> - Update message in xe_ras_log_wedged().
>>
>> v4:
>> - Replace XE_RAS_WEDGED to xe_ras_log_wedged. (Dnyaneshwar)
>> ---
>> drivers/gpu/drm/xe/xe_device.c | 13 +++++++------
>> 1 file changed, 7 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_device.c
>> b/drivers/gpu/drm/xe/xe_device.c
>> index b6e49309a99f..7538ac7c7dfb 100644
>> --- a/drivers/gpu/drm/xe/xe_device.c
>> +++ b/drivers/gpu/drm/xe/xe_device.c
>> @@ -62,6 +62,7 @@
>> #include "xe_pxp.h"
>> #include "xe_query.h"
>> #include "xe_ras.h"
>> +#include "xe_ras_log.h"
>> #include "xe_shrinker.h"
>> #include "xe_soc_remapper.h"
>> #include "xe_survivability_mode.h"
>> @@ -1428,12 +1429,12 @@ void xe_device_declare_wedged(struct
>> xe_device *xe)
>> if (!atomic_xchg(&xe->wedged.flag, 1)) {
>> xe->needs_flr_on_fini = true;
>> xe_pm_runtime_get_noresume(xe);
>> - drm_err(&xe->drm,
>> - "CRITICAL: Xe has declared device %s as wedged.\n"
>> - "IOCTLs and executions are blocked.\n"
>> - "For recovery procedure, refer
>> tohttps://docs.kernel.org/gpu/drm-uapi.html#device-wedging\n"
>> - "Please file a _new_ bug report
>> athttps://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n",
>> - dev_name(xe->drm.dev));
>> + xe_ras_log_wedged(xe, -EIO,
>
> Error code is changed for wedged.
> Please take a look at this patch [PATCH v2 1/2] drm/xe/guc:
> distinguish wedged from recoverable cancellation - Sk Anirban
> <https://lore.kernel.org/intel-xe/20260624194618.2793571-5-sk.anirban@intel.com/>
>
Those patches are called
after xe_device_declare_wedged()-->xe_gt_declare_wedged()-->xe_uc_declare_wedged(),
I need to take a look.
Thanks,
-/Mallesh
> Thanks
> Riana
>
>> + "CRITICAL: Xe has declared device %s as wedged.\n"
>> + "IOCTLs and executions are blocked.\n"
>> + "For recovery procedure, refer
>> tohttps://docs.kernel.org/gpu/drm-uapi.html#device-wedging\n"
>> + "Please file a _new_ bug report
>> athttps://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n",
>> + dev_name(xe->drm.dev));
>> }
>> for_each_gt(gt, xe, id)
next prev parent reply other threads:[~2026-07-06 23:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 11:55 [RFC PATCH v4 0/5] drm/xe: Structured RAS error logging infrastructure Mallesh Koujalagi
2026-06-30 11:55 ` [RFC PATCH v4 1/5] drm/xe: Add SIG_IDs for RAS error logging Mallesh Koujalagi
2026-06-30 14:25 ` Raag Jadav
2026-07-06 10:43 ` Mallesh, Koujalagi
2026-07-06 13:59 ` Michal Wajdeczko
2026-06-30 11:55 ` [RFC PATCH v4 2/5] drm/xe: Add RAS logging helpers Mallesh Koujalagi
2026-07-03 11:15 ` Tauro, Riana
2026-07-03 13:01 ` Mallesh, Koujalagi
2026-07-06 8:35 ` Tauro, Riana
2026-07-06 10:53 ` Mallesh, Koujalagi
2026-06-30 11:55 ` [RFC PATCH v4 3/5] drm/xe: use xe_ras_log_wedged macro in xe_device_declare_wedged Mallesh Koujalagi
2026-07-06 8:36 ` Tauro, Riana
2026-07-06 23:57 ` Mallesh, Koujalagi [this message]
2026-07-06 14:32 ` Michal Wajdeczko
2026-06-30 11:55 ` [RFC PATCH v4 4/5] drm/xe: Use RAS logging to report survivability mode Mallesh Koujalagi
2026-07-06 8:41 ` Tauro, Riana
2026-06-30 11:55 ` [RFC PATCH v4 5/5] drm/xe: Replace critical drm_err log with xe_ras_log_probe Mallesh Koujalagi
2026-07-06 15:38 ` Michal Wajdeczko
2026-06-30 13:12 ` ✗ CI.checkpatch: warning for drm/xe: Structured RAS error logging infrastructure (rev4) Patchwork
2026-06-30 13:13 ` ✓ CI.KUnit: success " Patchwork
2026-06-30 14:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-01 4:42 ` ✗ 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=21c1df90-0862-4056-ae65-4bcbce1640ef@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=matthew.brost@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sk.anirban@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=vinay.belgaumkar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox