public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Shekhar Chauhan <shekhar.chauhan@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: shekhar.chauhan@intel.com, ashutosh.dixit@intel.com
Subject: [PATCH] drm/xe/oa: Wa_14026633728
Date: Fri, 24 Apr 2026 13:43:54 +0530	[thread overview]
Message-ID: <20260424081354.3033523-1-shekhar.chauhan@intel.com> (raw)

For MERT_OA in CRI, the OA_Buffer is in device memory. The minimum
exponent needed for it is 8. Bump it up.

Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
---
 tests/intel/xe_oa.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
index 988c46df6..7bd9d17c4 100644
--- a/tests/intel/xe_oa.c
+++ b/tests/intel/xe_oa.c
@@ -2645,6 +2645,12 @@ 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: MERTOA buffer on CRI is in device memory,
+	 * minimum exponent to avoid overflow is 8 */
+	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


             reply	other threads:[~2026-04-24  8:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  8:13 Shekhar Chauhan [this message]
2026-04-24  8:17 ` [PATCH] drm/xe/oa: Wa_14026633728 Shekhar Chauhan
2026-04-24 13:15 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-24 13:22 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-24 14:37 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-24 17:03 ` ✓ i915.CI.Full: success " Patchwork
2026-04-24 19:34 ` [PATCH] " 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=20260424081354.3033523-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