From: sashiko-bot@kernel.org
To: "Umesh Nerlige Ramappa" <umesh.nerlige.ramappa@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report
Date: Fri, 21 Aug 2026 20:24:19 +0000 [thread overview]
Message-ID: <20260821202419.DA94F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260821200728.1048699-7-umesh.nerlige.ramappa@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The macro `oa_report_header_64bit` becomes unused and is left as dead code.
--
--- Patch [2]: [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report ---
commit 834ec77b5bb816bced6887fd353db954dc30486c
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
drm/xe/xe_oa: Avoid checking and setting fields in the OA report
This commit removes the workaround that checked and cleared specific fields
in the OA report buffer, as reports can now land out of order. Future patches
will introduce new logic to handle updated reports.
> diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> index 2e4a89ebf737a..020b27c642268 100644
> --- a/drivers/gpu/drm/xe/xe_oa.c
> +++ b/drivers/gpu/drm/xe/xe_oa.c
> @@ -216,42 +216,6 @@ static u32 xe_oa_hw_tail_read(struct xe_oa_stream *stream)
> #define oa_report_header_64bit(__s) \
> ((__s)->oa_buffer.format->header == HDR_64_BIT)
[Severity: Low]
This isn't a bug, but since oa_report_id(), oa_report_id_clear(),
oa_timestamp(), and oa_timestamp_clear() were removed by this patch, does
this leave the oa_report_header_64bit() macro unused?
> -static u64 oa_report_id(struct xe_oa_stream *stream, u32 report_offset)
> -{
> - struct iosys_map *map = &stream->oa_buffer.bo->vmap;
> -
> - return oa_report_header_64bit(stream) ?
> - xe_map_rd(stream->oa->xe, map, report_offset, u64) :
> - xe_map_rd(stream->oa->xe, map, report_offset, u32);
> -}
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260821200728.1048699-5-umesh.nerlige.ramappa@intel.com?part=2
next prev parent reply other threads:[~2026-08-21 20:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 20:07 [PATCH 0/3] Modify the SW tail logic in OA Umesh Nerlige Ramappa
2026-08-21 20:07 ` [PATCH 1/3] drm/xe/xe_oa: Clear status only if relevant bits are set Umesh Nerlige Ramappa
2026-08-21 20:07 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
2026-08-21 20:24 ` sashiko-bot [this message]
2026-08-21 20:07 ` [PATCH 3/3] drm/xe/xe_oa: Add a lag to the reports that is exported to user Umesh Nerlige Ramappa
2026-08-21 20:21 ` sashiko-bot
2026-08-21 20:14 ` ✓ CI.KUnit: success for Modify the SW tail logic in OA Patchwork
2026-08-21 21:03 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-21 22:35 ` ✓ Xe.CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-08-21 22:23 [PATCH 0/3] " Umesh Nerlige Ramappa
2026-08-21 22:23 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
2026-08-21 22:34 ` sashiko-bot
2026-08-24 15:39 ` Dixit, Ashutosh
2026-08-26 23:30 ` Umesh Nerlige Ramappa
2026-08-26 23:44 ` Dixit, Ashutosh
2026-08-06 22:47 [PATCH 0/3] Modify the SW tail logic in OA Umesh Nerlige Ramappa
2026-08-06 22:47 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
2026-07-30 23:35 [PATCH 0/3] Modify the SW tail logic in OA Umesh Nerlige Ramappa
2026-07-30 23:35 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
2026-07-22 21:54 [PATCH 0/3] Modify the SW tail logic in OA Umesh Nerlige Ramappa
2026-07-22 21:54 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
2026-07-21 23:48 [PATCH 0/3] Modify the SW tail logic in OA Umesh Nerlige Ramappa
2026-07-21 23:48 ` [PATCH 2/3] drm/xe/xe_oa: Avoid checking and setting fields in the OA report Umesh Nerlige Ramappa
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=20260821202419.DA94F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=umesh.nerlige.ramappa@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