Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shekhar Chauhan" <shekhar.chauhan@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/xe/xe3: Fix OAM stream broken on Xe3+
Date: Wed, 21 Oct 2026 05:39:37 +0000	[thread overview]
Message-ID: <sashiko-outbox-179811@kernel.org> (raw)
In-Reply-To: <20261021052333.1341575-2-shekhar.chauhan@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/xe/oa: tail address wrap helpers defined as macros despite v2 changelog
--

commit 5ceb7361283be3f44630db810b6ab0762b3744ab
Author: Shekhar Chauhan <shekhar.chauhan@intel.com>

drm/xe/xe3: Fix OAM stream broken on Xe3+

This commit prevents partial reports at the end of the oa buffer on Xe3+ oam
streams when overrun mode is enabled by rounding circ_size down to a multiple
of the report size.

> diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> index c9320feeafba8..f536fbccabb98 100644
> --- a/drivers/gpu/drm/xe/xe_oa.c
> +++ b/drivers/gpu/drm/xe/xe_oa.c
> @@ -1751,6 +1751,15 @@ static const struct file_operations xe_oa_fops = {
>  	.mmap		= xe_oa_mmap,
>  };
>  
> +#define oag_has_tail_address_wrap(stream) \
> +	(GRAPHICS_VER((stream)->oa->xe) >= 20 && \
> +	 (stream)->oa_unit->type == DRM_XE_OA_UNIT_TYPE_OAG)
> +
> +#define oam_has_tail_address_wrap(stream) \
> +	(MEDIA_VER((stream)->oa->xe) >= 30 && \
> +	 ((stream)->oa_unit->type == DRM_XE_OA_UNIT_TYPE_OAM || \
> +	  (stream)->oa_unit->type == DRM_XE_OA_UNIT_TYPE_OAM_SAG))

[Severity: Low]
This isn't a runtime bug, but the v2 note in the commit message states:

  v2: Fix checkpatch issues by using a static func instead of #define.

However, in drivers/gpu/drm/xe/xe_oa.c, oag_has_tail_address_wrap() and
oam_has_tail_address_wrap() (used by xe_oa_stream_init() when initializing an
oa stream) are still defined as preprocessor macros that evaluate their
stream argument multiple times.

Were the v2 changes converting oag_has_tail_address_wrap() and
oam_has_tail_address_wrap() into static functions accidentally left out of
the commit?

> +
>  static int xe_oa_stream_init(struct xe_oa_stream *stream,
>  			     struct xe_oa_open_param *param)
>  {

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261021052333.1341575-2-shekhar.chauhan@intel.com?part=1

  parent reply	other threads:[~2026-10-21  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  5:23 [PATCH v2] drm/xe/xe3: Fix OAM stream broken on Xe3+ Shekhar Chauhan
2026-10-21  5:29 ` ✗ CI.checkpatch: warning for drm/xe/xe3: Fix OAM stream broken on Xe3+ (rev3) Patchwork
2026-10-21  5:31 ` ✓ CI.KUnit: success " Patchwork
2026-10-21  5:33 ` [PATCH v2] drm/xe/xe3: Fix OAM stream broken on Xe3+ Shekhar Chauhan
2026-10-21  5:39 ` sashiko-bot [this message]
2026-10-21  6:14 ` ✓ Xe.CI.BAT: success for drm/xe/xe3: Fix OAM stream broken on Xe3+ (rev3) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2026-10-21  5:30 [PATCH v2] drm/xe/xe3: Fix OAM stream broken on Xe3+ Shekhar Chauhan

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=sashiko-outbox-179811@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shekhar.chauhan@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