Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@Intel.com>
To: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: michal.wajdeczko@intel.com
Subject: Re: [PATCH 06/12] drm/xe/reg_whitelist: Report whitelist overflow using structured xe_log API
Date: Tue, 8 Sep 2026 15:55:14 +0530	[thread overview]
Message-ID: <6b0f0346-51ba-4ba9-9f33-d7366ef84515@Intel.com> (raw)
In-Reply-To: <ca6d9176-df1f-4a4c-904e-80a1955056f8@intel.com>



On 26-Aug-26 3:52 PM, Mallesh, Koujalagi wrote:
> 
> On 20-08-2026 12:44 am, Dnyaneshwar Bhadane wrote:
>> Replace xe_gt_err() with xe_log_err() using the REGS component tag
>> when the maximum register whitelist slots are exhausted.
>>
>> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_reg_whitelist.c | 7 ++++---
>>   1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_reg_whitelist.c b/drivers/gpu/drm/ 
>> xe/xe_reg_whitelist.c
>> index cab1b578ca0e..d58c31b30199 100644
>> --- a/drivers/gpu/drm/xe/xe_reg_whitelist.c
>> +++ b/drivers/gpu/drm/xe/xe_reg_whitelist.c
>> @@ -14,6 +14,7 @@
>>   #include "xe_gt.h"
>>   #include "xe_gt_types.h"
>>   #include "xe_gt_printk.h"
>> +#include "xe_log.h"
>>   #include "xe_platform_types.h"
>>   #include "xe_reg_sr.h"
>>   #include "xe_rtp.h"
>> @@ -186,9 +187,9 @@ static int whitelist_apply_to_hwe(struct 
>> xe_hw_engine *hwe, struct xe_reg_sr *in
>>           };
>>           if (slot == RING_MAX_NONPRIV_SLOTS) {
>> -            xe_gt_err(hwe->gt,
>> -                  "hwe %s: maximum register whitelist slots (%d) 
>> reached, refusing to add more\n",
>> -                  hwe->name, RING_MAX_NONPRIV_SLOTS);
>> +            xe_log_err(hwe->gt, REGS, EPERM,
> 
> nit: xe_log takes negative error number. Errno should be -EOVERFLOW right?
This is good suggestion. I will update with -EOVERFLOW in next revision.
Thank you. >
> Thanks,
> 
> -/Mallesh
> 
>> +                   "hwe %s: maximum register whitelist slots (%d) 
>> reached, refusing to add more\n",
>> +                   hwe->name, RING_MAX_NONPRIV_SLOTS);
>>               break;
>>           }


  reply	other threads:[~2026-09-08 10:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 19:14 [PATCH 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:23   ` sashiko-bot
2026-08-26  9:50   ` Mallesh, Koujalagi
2026-09-08 10:23     ` Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-08-19 19:22   ` sashiko-bot
2026-08-26 10:09   ` Mallesh, Koujalagi
2026-09-08 10:24     ` Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 06/12] drm/xe/reg_whitelist: Report whitelist overflow " Dnyaneshwar Bhadane
2026-08-19 19:22   ` sashiko-bot
2026-08-26 10:22   ` Mallesh, Koujalagi
2026-09-08 10:25     ` Dnyaneshwar Bhadane [this message]
2026-08-19 19:14 ` [PATCH 07/12] drm/xe/reg_sr: Report save-restore errors " Dnyaneshwar Bhadane
2026-08-26 12:33   ` Mallesh, Koujalagi
2026-09-08 10:30     ` Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 08/12] drm/xe/pat: Assert pat.ops before dereferencing members Dnyaneshwar Bhadane
2026-08-19 19:22   ` sashiko-bot
2026-08-19 19:14 ` [PATCH 09/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-08-19 19:23   ` sashiko-bot
2026-08-19 19:14 ` [PATCH 10/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-08-19 19:27   ` sashiko-bot
2026-08-19 19:14 ` [PATCH 11/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-08-19 19:28   ` sashiko-bot
2026-08-26 10:29   ` Mallesh, Koujalagi
2026-09-08 10:26     ` Dnyaneshwar Bhadane
2026-08-19 19:14 ` [PATCH 12/12] drm/xe/vram: Report VRAM " Dnyaneshwar Bhadane
2026-08-19 19:29   ` sashiko-bot
2026-08-20  6:06     ` Dnyaneshwar Bhadane
2026-08-19 19:23 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to " Patchwork
2026-08-19 20:45 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-20  1:38 ` ✗ 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=6b0f0346-51ba-4ba9-9f33-d7366ef84515@Intel.com \
    --to=dnyaneshwar.bhadane@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@intel.com \
    --cc=michal.wajdeczko@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