Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: [PATCH i-g-t] tests/intel/xe_oa: Fix checks for whitlisted oa registers
Date: Mon, 15 Jun 2026 19:01:20 -0700	[thread overview]
Message-ID: <20260616020120.46894-1-ashutosh.dixit@intel.com> (raw)

OASTATUS register is not used by UMD's and the plan is to discontinue
whitelisting that in the kernel. Also, OAHEADPTR is written to nonpriv
slots. So check that OAG_MMIOTRIGGER and OAG_OAHEADPTR are whitelisted for
OAG and remove the check for OASTATUS.

Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
---
 tests/intel/xe_oa.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
index e59fe953b0..68c7537d38 100644
--- a/tests/intel/xe_oa.c
+++ b/tests/intel/xe_oa.c
@@ -3833,12 +3833,12 @@ test_whitelisted_registers_userspace_config(void)
 	xe_oa_remove_config(drm_fd, config_id);
 }
 
-#define OAG_OASTATUS (0xdafc)
+#define OAG_OAHEADPTR (0xdb00)
 #define OAG_MMIOTRIGGER (0xdb1c)
 
 static const uint32_t oa_wl[] = {
 	OAG_MMIOTRIGGER,
-	OAG_OASTATUS,
+	OAG_OAHEADPTR,
 };
 
 static const uint32_t nonpriv_slot_offsets[] = {
-- 
2.54.0


             reply	other threads:[~2026-06-16  2:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  2:01 Ashutosh Dixit [this message]
2026-06-16  2:56 ` ✓ Xe.CI.BAT: success for tests/intel/xe_oa: Fix checks for whitlisted oa registers (rev2) Patchwork
2026-06-16  3:08 ` ✓ i915.CI.BAT: " Patchwork
2026-06-16  4:08 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-16 13:00 ` ✗ i915.CI.Full: failure " Patchwork
2026-06-16 23:09 ` [PATCH i-g-t] tests/intel/xe_oa: Fix checks for whitlisted oa registers Umesh Nerlige Ramappa
  -- strict thread matches above, loose matches on Subject: below --
2026-05-12 16:26 Ashutosh Dixit
2026-05-13 17:53 ` 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=20260616020120.46894-1-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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