Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Arvind Yadav <arvind.yadav@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <rodrigo.vivi@intel.com>, <badal.nilawar@intel.com>,
	<himal.prasad.ghimiray@intel.com>,
	<dnyaneshwar.bhadane@intel.com>, <mallesh.koujalagi@intel.com>,
	<matthew.brost@intel.com>
Subject: Re: [PATCH v6 1/4] drm/xe/log: Add GUCSUBMIT component
Date: Wed, 2 Sep 2026 14:33:50 +0200	[thread overview]
Message-ID: <38edbb95-d9bb-4201-9a5e-829079de789e@intel.com> (raw)
In-Reply-To: <20260901063059.2547247-2-arvind.yadav@intel.com>



On 9/1/2026 8:30 AM, Arvind Yadav wrote:
> Add a GUCSUBMIT component for structured SIGID logging.
> 
> GuC submit failures can still map to an existing SIGID, but using the
> generic GT component hides the source of the report. Add GUCSUBMIT as
> a DRIVER component and map it to XE_SIGID_GT_TDR.

nit: can we improve the commit message? maybe

 "The proper SIGID for the GuC submission failures is GT_TDR, but use
 "of the generic GT component may hide the real source of the report.
 "Add GUCSUBMIT as a DRIVER component and map it to XE_SIGID_GT_TDR.
> 
> Cc: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Suggested-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Arvind Yadav <arvind.yadav@intel.com>
> ---
> v6:
>  - Moved GUCSUBMIT from DRIVER_FIRMWARE to DRIVER, since GuC submit
>    is a driver submission component and not a firmware component.
>    (Michal)
> 
>  drivers/gpu/drm/xe/abi/xe_log_abi.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/xe/abi/xe_log_abi.h b/drivers/gpu/drm/xe/abi/xe_log_abi.h
> index d6105520173e..91fe983ad917 100644
> --- a/drivers/gpu/drm/xe/abi/xe_log_abi.h
> +++ b/drivers/gpu/drm/xe/abi/xe_log_abi.h
> @@ -144,6 +144,7 @@ enum xe_log_location_bits {
>  	define(DRIVER, 4, RTP, SW, "Register Table Processing")			\
>  	define(DRIVER, 5, WA, SW, "Workarounds")				\
>  	define(DRIVER, 6, PAGEFAULT, MEM_FAULT, "Page Fault")			\
> +	define(DRIVER, 7, GUCSUBMIT, GT_TDR, "GuC Submit")			\

nit: we can have "GuC Submission" as a full name

Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>  	/* */									\
>  	define(DRIVER_HARDWARE, 1, REGS, IO_BUS, "Registers")			\
>  	define(DRIVER_HARDWARE, 2, GGTT, IO_BUS, "Global GTT")			\


  reply	other threads:[~2026-09-02 12:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  6:30 [PATCH v6 0/4] drm/xe: Report GT TDR and VM rebind faults using SIGID Arvind Yadav
2026-09-01  6:30 ` [PATCH v6 1/4] drm/xe/log: Add GUCSUBMIT component Arvind Yadav
2026-09-02 12:33   ` Michal Wajdeczko [this message]
2026-09-03  3:16     ` Yadav, Arvind
2026-09-01  6:30 ` [PATCH v6 2/4] drm/xe/guc: Report reset failure using SIGID Arvind Yadav
2026-09-02 12:36   ` Michal Wajdeczko
2026-09-01  6:30 ` [PATCH v6 3/4] drm/xe/svm: Report terminal page-fault failures " Arvind Yadav
2026-09-02 11:54   ` Mallesh, Koujalagi
2026-09-02 12:43   ` Michal Wajdeczko
2026-09-03  3:44     ` Yadav, Arvind
2026-09-01  6:30 ` [PATCH v6 4/4] drm/xe/gt: Report GT reset failure " Arvind Yadav
2026-09-02 11:45   ` Mallesh, Koujalagi
2026-09-02 12:51   ` Michal Wajdeczko
2026-09-03  4:32     ` Yadav, Arvind
2026-09-01  6:39 ` ✓ CI.KUnit: success for drm/xe: Report GT TDR and VM rebind faults using SIGID (rev6) Patchwork
2026-09-01  7:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-01  8:27 ` ✗ 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=38edbb95-d9bb-4201-9a5e-829079de789e@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=arvind.yadav@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@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