From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"talesam@gmail.com" <talesam@gmail.com>
Subject: Re: [PATCH] drm/xe: Add and use TLBINVAL component
Date: Wed, 23 Sep 2026 18:39:33 +0200 [thread overview]
Message-ID: <8afcd21a-4ac2-46a5-a698-524b5ff8519d@intel.com> (raw)
In-Reply-To: <ca660eb96bacc75620c6c58a521cc28c445ea9e7.camel@intel.com>
On 9/22/2026 9:22 PM, Summers, Stuart wrote:
> On Tue, 2026-09-22 at 19:19 +0200, Michal Wajdeczko wrote:
>> Replace the existing TLB invalidation error message with a new one
>> based on the xe_log_err() macro and use the dedicated TLBINVAL log
>> component.
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> ---
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Cc: Tales A. Mendonça <talesam@gmail.com>
>> ---
>> drivers/gpu/drm/xe/abi/xe_log_abi.h | 1 +
>> drivers/gpu/drm/xe/xe_tlb_inval.c | 6 +++---
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/abi/xe_log_abi.h
>> b/drivers/gpu/drm/xe/abi/xe_log_abi.h
>> index 526aadf85fe9..adb3c2128251 100644
>> --- a/drivers/gpu/drm/xe/abi/xe_log_abi.h
>> +++ b/drivers/gpu/drm/xe/abi/xe_log_abi.h
>> @@ -145,6 +145,7 @@ enum xe_log_location_bits {
>> define(DRIVER, 5, WA, SW,
>> "Workarounds") \
>> define(DRIVER, 6, PAGEFAULT, MEM_FAULT, "Page
>> Fault") \
>> define(DRIVER, 7, GUCSUBMIT, GT_TDR, "GuC
>> Submission") \
>> + define(DRIVER, 8, TLBINVAL, GT_TDR, "TLB
>> Invalidation") \
>> /*
>> */
>> \
>> define(DRIVER_HARDWARE, 1, REGS, IO_BUS,
>> "Registers") \
>> define(DRIVER_HARDWARE, 2, GGTT, IO_BUS, "Global
>> GTT") \
>> diff --git a/drivers/gpu/drm/xe/xe_tlb_inval.c
>> b/drivers/gpu/drm/xe/xe_tlb_inval.c
>> index dd1030de9ab6..da629d410829 100644
>> --- a/drivers/gpu/drm/xe/xe_tlb_inval.c
>> +++ b/drivers/gpu/drm/xe/xe_tlb_inval.c
>> @@ -11,6 +11,7 @@
>> #include "xe_gt_types.h"
>> #include "xe_guc_ct.h"
>> #include "xe_guc_tlb_inval.h"
>> +#include "xe_log.h"
>> #include "xe_mmio.h"
>> #include "xe_pm.h"
>> #include "xe_tlb_inval.h"
>> @@ -86,9 +87,8 @@ static void xe_tlb_inval_fence_timeout(struct
>> work_struct *work)
>> break;
>>
>> trace_xe_tlb_inval_fence_timeout(xe, fence);
>> - drm_err(&xe->drm,
>> - "TLB invalidation fence timeout, seqno=%d
>> recv=%d",
>> - fence->seqno, tlb_inval->seqno_recv);
>> + xe_log_err(xe, TLBINVAL, -ETIME, "fence timeout,
>> seqno=%d recv=%d",
>
> Can we keep the "TLB invalidation" piece here since that's a little
> easier for grepping when manually debugging?
this would be little redundant, as xe_log_err will emit dmesg like this:
[drm] *ERROR* SIGID=106 (-ETIME) TLBINVAL: fence timeout...
vs
[drm] *ERROR* SIGID=106 (-ETIME) TLBINVAL: TLB invalidation fence timeout...
>
> And slight nitpick.. Can we use a variable for -ETIME here since we're
> now using it in two places in case we want to change in the future?
>
> Otherwise the patch looks good:
> Reviewed-by: Stuart Summers <stuart.summers@intel.com>
>
> Thanks,
> Stuart
>
>> + fence->seqno, tlb_inval->seqno_recv);
>>
>> fence->base.error = -ETIME;
>> xe_tlb_inval_fence_signal(fence);
>
next prev parent reply other threads:[~2026-09-23 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:19 [PATCH] drm/xe: Add and use TLBINVAL component Michal Wajdeczko
2026-09-22 18:58 ` ✓ CI.KUnit: success for " Patchwork
2026-09-22 19:22 ` [PATCH] " Summers, Stuart
2026-09-23 16:39 ` Michal Wajdeczko [this message]
2026-09-23 17:49 ` Summers, Stuart
2026-09-22 21:05 ` ✗ Xe.CI.BAT: failure for " Patchwork
2026-09-23 8:59 ` ✗ 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=8afcd21a-4ac2-46a5-a698-524b5ff8519d@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stuart.summers@intel.com \
--cc=talesam@gmail.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