Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<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>,
	"Zhanjun Dong" <zhanjun.dong@intel.com>
Subject: Re: [PATCH v4 0/1] Maintenence of devcoredump <-> GuC-Err-Capture plumbing
Date: Tue, 21 Jan 2025 18:15:49 -0500	[thread overview]
Message-ID: <Z5AqpemmzmBX2755@intel.com> (raw)
In-Reply-To: <20250121190935.1984508-1-alan.previn.teres.alexis@intel.com>

On Tue, Jan 21, 2025 at 11:09:34AM -0800, Alan Previn wrote:
> The GuC-Error-Capture is currently reaching into xe_devcoredump
> structure to store its own place-holder snaphot to workaround
> the race between G2H-Error-Capture-Notification vs Drm-Scheduler
> triggering GuC-Submission-exec-queue-timeout/kill.
> 
> Part of that race workaround design included GuC-Error-Capture taking
> on some of the front-end functions for xe_hw_engine_snapshot
> generation because of the orthogonal debugfs for raw dumps of engine
> registers without any job association. We want this to also be handled,
> even if indirectly, by GuC-Error-Capture since there is a lot to manage
> when it comes to reading and printing the register lists.
> 
> However, logically speaking, GuC-Error-Capture node management,
> despite being the majority of an engine-snapshot work, is still
> a subset of xe_hw_engine_snapshot.
> 
> This series intends to re-design the plumbing for future

A 'series' of 1 patch is not a series. Cover letter is not needed.

However, this patch is the size of a series and it should be
split. I'm really surprised that someone went over and
*really* reviewed it.

Even the subject of the patch doesn't make a lot of sense to me.
I don't even know what to write in the pull-request with a patch
like this.

Please break this in small patches.

> maintenence and scalability, rearranging the layering
> back to what its should be (xe_devcoredump_snapshot owns
> xe_hw_engine_snapshot owns xe_guc_capture_snapshot)..
> 
> Alan Previn (1):
>   drm/xe/guc/capture: Maintenence of devcoredump <-> GuC-Err-Capture
>     plumbing
> 
>  drivers/gpu/drm/xe/xe_devcoredump.c           |   3 -
>  drivers/gpu/drm/xe/xe_devcoredump_types.h     |   6 -
>  drivers/gpu/drm/xe/xe_guc_capture.c           | 406 ++++++++----------
>  drivers/gpu/drm/xe/xe_guc_capture.h           |  10 +-
>  .../drm/xe/xe_guc_capture_snapshot_types.h    |  68 +++
>  drivers/gpu/drm/xe/xe_guc_submit.c            |  21 +-
>  drivers/gpu/drm/xe/xe_hw_engine.c             | 117 +++--
>  drivers/gpu/drm/xe/xe_hw_engine.h             |   4 +-
>  drivers/gpu/drm/xe/xe_hw_engine_types.h       |  13 +-
>  9 files changed, 359 insertions(+), 289 deletions(-)
>  create mode 100644 drivers/gpu/drm/xe/xe_guc_capture_snapshot_types.h
> 
> 
> base-commit: cfa9d40db8c30d894171010fe765d96e9bc6a47e
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2025-01-21 23:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 19:09 [PATCH v4 0/1] Maintenence of devcoredump <-> GuC-Err-Capture plumbing Alan Previn
2025-01-21 19:09 ` [PATCH v4 1/1] drm/xe/guc/capture: " Alan Previn
2025-01-21 20:52 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-21 20:52 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-21 20:54 ` ✓ CI.KUnit: success " Patchwork
2025-01-21 21:10 ` ✓ CI.Build: " Patchwork
2025-01-21 21:12 ` ✓ CI.Hooks: " Patchwork
2025-01-21 21:14 ` ✓ CI.checksparse: " Patchwork
2025-01-21 21:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-21 23:15 ` Rodrigo Vivi [this message]
2025-01-23 18:01   ` [PATCH v4 0/1] " Teres Alexis, Alan Previn
2025-01-28 20:33     ` Teres Alexis, Alan Previn
2025-01-22  4:31 ` ✗ Xe.CI.Full: failure for " 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=Z5AqpemmzmBX2755@intel.com \
    --to=rodrigo.vivi@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=zhanjun.dong@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