From: Matthew Brost <matthew.brost@intel.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: Brian Nguyen <brian3.nguyen@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Implement print vfunc for page fault info logging
Date: Fri, 25 Sep 2026 19:18:04 -0700 [thread overview]
Message-ID: <arcrXAJy/bzijpdp@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260925233853.399E01F000FF@smtp.kernel.org>
On Fri, Sep 25, 2026 at 11:38:52PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] xe: log interleaving and redundant prefixes due to split print calls
> --
>
> commit 114cd7fd731f9ee67d8c36081ae1b0f44d9be562
> Author: Brian Nguyen <brian3.nguyen@intel.com>
>
> drm/xe: Implement print vfunc for page fault info logging
>
> This commit adds a print vfunc to xe_pagefault_ops to let producer
> backends log specific relevant debug info. This keeps the consumer
> layer free of backend-specific formatting logic, with consumer-specific
> prints handled separately.
>
> > diff --git a/drivers/gpu/drm/xe/xe_pagefault.c b/drivers/gpu/drm/xe/xe_pagefault.c
> > --- a/drivers/gpu/drm/xe/xe_pagefault.c
> > +++ b/drivers/gpu/drm/xe/xe_pagefault.c
> > @@ -607,35 +606,9 @@ static const char *xe_pagefault_error_to_str(enum xe_pagefault_error error)
> >
> > static void xe_pagefault_print(struct xe_pagefault *pf)
> > {
>
> [ ... ]
>
> > - FIELD_GET(XE_PAGEFAULT_ENGINE_INSTANCE_MASK,
> > - pf->consumer.engine_class_instance),
> > - FIELD_GET(XE_PAGEFAULT_SRCID_MASK,
> > - pf->consumer.id),
> > + xe_gt_assert(pf->gt, pf->producer.ops->print);
> > + pf->producer.ops->print(pf);
> > + xe_gt_info(pf->gt, "\tError: %s\n",
> > xe_pagefault_error_to_str(xe_pagefault_get_error(pf)));
> > }
>
> [Severity: Low]
> Does this split print call cause log interleaving and redundant prefixes?
>
> Because the error string is now logged with a separate call to xe_gt_info()
> in xe_pagefault_print(), it will be printed as an isolated log entry with
> its own prefix, rather than forming a continuous atomic block with the fault
> details from the producer print vfunc.
>
> This disrupts the formatting of the page fault debug info, introducing
> redundant logging prefixes in the middle of what used to be a single
> continuous multiline log block. It also creates a risk of concurrent kernel
> messages interleaving with the output.
>
This is valid too. So either make print accept the output of
xe_pagefault_error_to_str as an argument and print the entire thing in
one shot.
Matt
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260925232757.3456172-2-brian3.nguyen@intel.com?part=1
next prev parent reply other threads:[~2026-09-26 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 23:27 [PATCH] drm/xe: Implement print vfunc for page fault info logging Brian Nguyen
2026-09-25 23:38 ` sashiko-bot
2026-09-26 2:18 ` Matthew Brost [this message]
2026-09-28 17:27 ` Nguyen, Brian3
2026-09-25 23:53 ` Matthew Brost
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=arcrXAJy/bzijpdp@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=brian3.nguyen@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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