Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <dri-devel@lists.freedesktop.org>,
	Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	John Harrison <john.c.harrison@intel.com>,
	 Matthew Brost <matthew.brost@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v7 6/6] drm/xe/guc: Update comments on GuC-Err-Capture flows
Date: Tue, 11 Feb 2025 18:09:16 -0500	[thread overview]
Message-ID: <850c82d7-cdcc-4182-b7db-61f0d38e5a2f@intel.com> (raw)
In-Reply-To: <20250210233254.419587-7-alan.previn.teres.alexis@intel.com>



On 2025-02-10 6:32 p.m., Alan Previn wrote:
> Update the comments on GuC-Err-Capture flows with the
> updated function names.
> 
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_guc_capture.c | 19 +++++++++++--------
>   1 file changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_capture.c b/drivers/gpu/drm/xe/xe_guc_capture.c
> index 746d3b21b18b..15f9b08ff7bb 100644
> --- a/drivers/gpu/drm/xe/xe_guc_capture.c
> +++ b/drivers/gpu/drm/xe/xe_guc_capture.c
> @@ -905,22 +905,25 @@ guc_capture_init_node(struct xe_guc *guc, struct xe_guc_capture_snapshot *node)
>    *                   list. This list is used for matchup and printout by xe_devcoredump_read
>    *                   and xe_engine_snapshot_print, (when user invokes the devcoredump sysfs).
>    *
> - * GUC --> notify context reset:
> - * -----------------------------
> + * DRM Scheduler job-timeout OR GuC-notify guc-id reset:
> + * -----------------------------------------------------
>    *     --> guc_exec_queue_timedout_job
> - *                   L--> xe_devcoredump
> + *               L--> xe_guc_capture_snapshot_store_manual_job (if GuC didn't report an
> + *                    error capture node for this job)
> + *               L--> xe_devcoredump
>    *                          L--> devcoredump_snapshot
> - *                               --> xe_hw_engine_snapshot_capture
> - *                               --> xe_engine_manual_capture(For manual capture)
> + *                               --> xe_engine_snapshot_capture_for_queue
>    *
> - * User Sysfs / Debugfs
> - * --------------------
> - *      --> xe_devcoredump_read->
> + * User Devcoredump Sysfs
> + * ----------------------
> + *      --> xe_devcoredump_read-> (user cats devcoredump)
>    *             L--> xxx_snapshot_print
>    *                    L--> xe_hw_engine_print --> xe_hw_engine_snapshot_print
>    *                          L--> xe_guc_capture_snapshot_print
				L--> hw_engine_snapshot_capture
     				     xe_guc_capture_snapshot_manual_hwe
				     // The new function which do manual capture without job
And, for debugfs, it did not calls xe_devcoredump_read...
instead, by "hw_engines". Shall we mention debugfs call 
xe_hw_engine_print directly?

Other than that, LGTM
Reviewed-by: Zhanjun Dong <zhanjun.dong@intel.com>


>    *                               Print register lists values saved in matching
>    *                               node from guc->capture->outlist
> + *      --> xe_devcoredump_free (when user clears the dump)
> + *             L--> xe_devcoredump_snapshot_free --> xe_guc_capture_put_matched_nodes
>    *
>    */
>   


  reply	other threads:[~2025-02-11 23:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 23:32 [PATCH v7 0/6] Maintenence of devcoredump <-> GuC-Err-Capture plumbing Alan Previn
2025-02-10 23:32 ` [PATCH v7 1/6] drm/xe/guc: Rename __guc_capture_parsed_output Alan Previn
2025-02-10 23:32 ` [PATCH v7 2/6] drm/xe/guc: Don't store capture nodes in xe_devcoredump_snapshot Alan Previn
2025-02-10 23:32 ` [PATCH v7 3/6] drm/xe/guc: Split engine state print between xe_hw_engine vs xe_guc_capture Alan Previn
2025-02-11 22:48   ` Dong, Zhanjun
2025-02-12 18:50     ` Teres Alexis, Alan Previn
2025-02-10 23:32 ` [PATCH v7 4/6] drm/xe/guc: Move xe_hw_engine_snapshot creation back to xe_hw_engine.c Alan Previn
2025-02-12 17:19   ` Dong, Zhanjun
2025-02-10 23:32 ` [PATCH v7 5/6] drm/xe/xe_hw_engine: Update xe_hw_engine capture for debugfs/gt_reset Alan Previn
2025-02-11 17:34   ` Teres Alexis, Alan Previn
2025-02-12 18:24     ` Dong, Zhanjun
2025-02-10 23:32 ` [PATCH v7 6/6] drm/xe/guc: Update comments on GuC-Err-Capture flows Alan Previn
2025-02-11 23:09   ` Dong, Zhanjun [this message]
2025-02-12 18:54     ` Teres Alexis, Alan Previn
2025-02-11  0:38 ` ✓ CI.Patch_applied: success for Maintenence of devcoredump <-> GuC-Err-Capture plumbing Patchwork
2025-02-11  0:38 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-11  0:39 ` ✓ CI.KUnit: success " Patchwork
2025-02-11  0:56 ` ✓ CI.Build: " Patchwork
2025-02-11  0:57 ` ✗ CI.Hooks: failure " Patchwork
2025-02-11  0:58 ` ✗ CI.checksparse: warning " Patchwork
2025-02-11  1:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-11 13:01 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-13  0:56   ` Teres Alexis, Alan Previn

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=850c82d7-cdcc-4182-b7db-61f0d38e5a2f@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@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