From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Mallesh Koujalagi <mallesh.koujalagi@intel.com>,
<intel-xe@lists.freedesktop.org>, <rodrigo.vivi@intel.com>,
<matthew.brost@intel.com>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<vinay.belgaumkar@intel.com>, <riana.tauro@intel.com>,
<karthik.poosa@intel.com>, <sk.anirban@intel.com>,
<raag.jadav@intel.com>, <aravind.iddamsetty@linux.intel.com>
Subject: Re: [PATCH 3/4] drm/xe/pcode: Improve pcode timeout logging
Date: Thu, 6 Aug 2026 16:42:53 +0200 [thread overview]
Message-ID: <82169f77-5128-49ca-a375-58aaa0f09bdb@intel.com> (raw)
In-Reply-To: <20260806110039.1245282-9-mallesh.koujalagi@intel.com>
On 8/6/2026 1:00 PM, Mallesh Koujalagi wrote:
> Use xe_log_err() for pcode timeout errors instead of drm_err(). This
s/pcode/PCODE ?
> adds PCODE component tag, making timeout issues easier to detect and
> track with automated tools.
>
> Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pcode.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pcode.c b/drivers/gpu/drm/xe/xe_pcode.c
> index c492737242d3..b5a59a227167 100644
> --- a/drivers/gpu/drm/xe/xe_pcode.c
> +++ b/drivers/gpu/drm/xe/xe_pcode.c
> @@ -220,8 +220,8 @@ int xe_pcode_request(struct xe_tile *tile, u32 mbox, u32 request,
> * requests, and for any quirks of the PCODE firmware that delays
> * the request completion.
> */
> - drm_err(&tile_to_xe(tile)->drm,
> - "PCODE timeout, retrying with preemption disabled\n");
> + xe_log_err(tile, PCODE, -ETIMEDOUT,
> + "PCODE timeout, retrying with preemption disabled\n");
drop the "PCODE" prefix, as xe_log_err() will decorate dmesg with "PCODE: " for you
> preempt_disable();
> ret = pcode_try_request(tile, mbox, request, reply_mask, reply, &status,
> true, 50 * 1000, true);
next prev parent reply other threads:[~2026-08-06 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:00 [PATCH 0/4] drm/xe: Adopt xe_log SIGID API for structured error reporting Mallesh Koujalagi
2026-08-06 11:00 ` [PATCH 1/4] drm/xe/log: DO NOT REVIEW Mallesh Koujalagi
2026-08-06 11:00 ` [PATCH 2/4] drm/xe: Use xe_log SIGID API for probe-path error reporting Mallesh Koujalagi
2026-08-06 17:52 ` Michal Wajdeczko
2026-08-10 23:28 ` Umesh Nerlige Ramappa
2026-08-11 21:14 ` Bhadane, Dnyaneshwar
2026-08-06 11:00 ` [PATCH 3/4] drm/xe/pcode: Improve pcode timeout logging Mallesh Koujalagi
2026-08-06 14:42 ` Michal Wajdeczko [this message]
2026-08-06 11:00 ` [PATCH 4/4] drm/xe/sysctrl: Add better sysctrl error reporting Mallesh Koujalagi
2026-08-06 14:41 ` Michal Wajdeczko
2026-08-07 8:48 ` Mallesh, Koujalagi
2026-08-06 19:14 ` Umesh Nerlige Ramappa
2026-08-07 8:59 ` Mallesh, Koujalagi
2026-08-06 11:07 ` ✗ CI.checkpatch: warning for drm/xe: Adopt xe_log SIGID API for structured " Patchwork
2026-08-06 11:08 ` ✓ CI.KUnit: success " Patchwork
2026-08-06 12:13 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-06 20:44 ` ✓ Xe.CI.FULL: " 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=82169f77-5128-49ca-a375-58aaa0f09bdb@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.