From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v27 6/6] drm/xe/guc: Save manual engine capture into capture list
Date: Fri, 4 Oct 2024 17:42:33 +0000 [thread overview]
Message-ID: <2a0ef63683a1c662c92e7f3413fd90245e0a47a5.camel@intel.com> (raw)
In-Reply-To: <ec4f06dabf239413e8d57b0a16e8303083853811.camel@intel.com>
On Fri, 2024-10-04 at 10:38 -0700, Teres Alexis, Alan Previn wrote:
> As per offline conversation just now, since our last thorough review in rev18,
> we notice many trivial changes that are not required at all that got accidentally
> included as a result of ongoing offline debugging work that you forgot to remove.
> I'll highlight them below as part of this review. Looking forward for next rev.
>
>
>
> On Thu, 2024-10-03 at 20:24 -0700, Zhanjun Dong wrote:
> > Save manual engine capture into capture list.
> > This removes duplicate register definitions across manual-capture vs
> > guc-err-capture.
> >
> >
> > -void xe_guc_capture_free(struct xe_guc *guc)
> > +void xe_guc_capture_put_matched_nodes(struct xe_guc *guc)
> > {
> > struct xe_device *xe = guc_to_xe(guc);
> > struct xe_devcoredump *devcoredump = &xe->devcoredump;
> > - struct __guc_capture_parsed_output *n = devcoredump->snapshot.matched_node;
> alan: all the changes in this function doesnt change the implementation, usage or behavior
> since Patch #5 - so we can just move these changes directly into patch #5. The name change is
> the one thing i did want to see since "free" is the opposite of "alloc" but we are not
> freeing content, we are returning a node we had "get" previously.
> >
> > - if (n) {
> > - guc_capture_remove_stale_matches_from_list(guc->capture, n);
> > - guc_capture_free_outlist_node(guc->capture, n);
> > + if (devcoredump->snapshot.matched_node) {
> > + guc_capture_remove_stale_matches_from_list(guc->capture,
> > + devcoredump->snapshot.matched_node);
> > + guc_capture_free_outlist_node(guc->capture, devcoredump->snapshot.matched_node);
> > +
> > + devcoredump->snapshot.matched_node = NULL;
> > }
> > - devcoredump->snapshot.matched_node = NULL;
alan: WRT to bringing this hunk into Pach #5, i am okay with you retaining the RB in Patch #5 if not other changes.
(same as the earlier comment in my last reply of this patch)
> > }
> >
> > /*
> alan:snip
next prev parent reply other threads:[~2024-10-04 17:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 3:23 [PATCH v27 0/6] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-10-04 3:23 ` [PATCH v27 1/6] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-10-04 3:23 ` [PATCH v27 2/6] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-10-04 3:23 ` [PATCH v27 3/6] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-10-04 3:23 ` [PATCH v27 4/6] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-10-04 3:23 ` [PATCH v27 5/6] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-10-04 3:24 ` [PATCH v27 6/6] drm/xe/guc: Save manual engine capture into capture list Zhanjun Dong
2024-10-04 17:38 ` Teres Alexis, Alan Previn
2024-10-04 17:42 ` Teres Alexis, Alan Previn [this message]
2024-10-04 23:17 ` Teres Alexis, Alan Previn
2024-10-04 3:31 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev27) Patchwork
2024-10-04 3:31 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-04 3:32 ` ✓ CI.KUnit: success " Patchwork
2024-10-04 3:44 ` ✓ CI.Build: " Patchwork
2024-10-04 3:46 ` ✓ CI.Hooks: " Patchwork
2024-10-04 3:47 ` ✓ CI.checksparse: " Patchwork
2024-10-04 4:09 ` ✓ CI.BAT: " Patchwork
2024-10-04 4:57 ` ✗ CI.FULL: failure " Patchwork
2024-10-04 14:37 ` Dong, Zhanjun
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=2a0ef63683a1c662c92e7f3413fd90245e0a47a5.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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