From: Shekhar Chauhan <shekhar.chauhan@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: shekhar.chauhan@intel.com, ashutosh.dixit@intel.com
Subject: [PATCH v2] tests/intel/xe_oa: Wa_14026633728
Date: Mon, 27 Apr 2026 10:30:02 +0530 [thread overview]
Message-ID: <20260427050002.3391994-1-shekhar.chauhan@intel.com> (raw)
For MERTOA in CRI, oa buffer can be in device memory. Because of slower
device mem access, OA exponent values lower than 8 can result in buffer
overflows. Bump the OA exponent value.
v2: Fix commit title, description and code description.
Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
---
tests/intel/xe_oa.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
index 988c46df6..cbc1e0d3e 100644
--- a/tests/intel/xe_oa.c
+++ b/tests/intel/xe_oa.c
@@ -2645,6 +2645,16 @@ test_non_zero_reason(const struct drm_xe_oa_unit *oau, size_t oa_buffer_size)
{
/* ~20 micro second period */
int oa_exponent = max_oa_exponent_for_period_lte(20000);
+
+ /*
+ * Wa_14026633728: For MERTOA in CRI, oa buffer can be in device memory.
+ * Because of slower device mem access, OA exponent values lower than 8 can
+ * result in buffer overflows.
+ */
+
+ if (oau->oa_unit_type == DRM_XE_OA_UNIT_TYPE_MERT && IS_CRESCENTISLAND(devid))
+ oa_exponent = max(oa_exponent, 8);
+
struct intel_xe_perf_metric_set *test_set = oa_unit_metric_set(oau);
uint64_t fmt = test_set->perf_oa_format;
size_t report_size = get_oa_format(fmt).size;
--
2.53.0
next reply other threads:[~2026-04-27 5:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 5:00 Shekhar Chauhan [this message]
2026-04-27 6:04 ` ✓ i915.CI.BAT: success for tests/intel/xe_oa: Wa_14026633728 Patchwork
2026-04-27 6:09 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-27 6:49 ` [PATCH v2] " Dixit, Ashutosh
2026-04-28 17:14 ` Dixit, Ashutosh
2026-04-27 12:21 ` ✗ Xe.CI.FULL: failure for " Patchwork
2026-04-28 5:28 ` ✓ Xe.CI.BAT: success for tests/intel/xe_oa: Wa_14026633728 (rev2) Patchwork
2026-04-28 5:53 ` ✓ i915.CI.BAT: " Patchwork
2026-04-28 11:51 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-28 12:17 ` ✗ i915.CI.Full: " Patchwork
2026-04-28 17:37 ` [PATCH v2] tests/intel/xe_oa: Wa_14026633728 Gustavo Sousa
2026-04-28 17:51 ` Dixit, Ashutosh
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=20260427050002.3391994-1-shekhar.chauhan@intel.com \
--to=shekhar.chauhan@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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