From: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: riana.tauro@intel.com, anshuman.gupta@intel.com,
mallesh.koujalagi@intel.com, raag.jadav@intel.com,
soham.purkait@intel.com,
Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
Subject: [PATCH v2 8/8] tests/intel/xe_err_injection: add CRI GPU requirement check
Date: Thu, 20 Aug 2026 17:46:00 +0530 [thread overview]
Message-ID: <20260820121600.75052-9-ravi.kishore.koppuravuri@intel.com> (raw)
In-Reply-To: <20260820121600.75052-1-ravi.kishore.koppuravuri@intel.com>
Add support to verify the CRI GPU and skips test gracefully
on non-cri platforms
Signed-off-by: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
---
tests/intel/xe_err_injection.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/tests/intel/xe_err_injection.c b/tests/intel/xe_err_injection.c
index 13a316c74..ccc19724c 100644
--- a/tests/intel/xe_err_injection.c
+++ b/tests/intel/xe_err_injection.c
@@ -20,6 +20,7 @@
#include "igt.h"
#include "lib/igt_drm_netlink.h"
+#include "lib/intel_chipset.h"
#include "lib/intel_reg.h"
#include "lib/intel_compute.h"
@@ -544,6 +545,14 @@ static void l2_bank_single_corr_err_injection(struct xe_mmio *mmio, int fd)
CLEANUP_ON_ERROR(ctx, fw_handle);
}
+static void igt_require_cri(int fd)
+{
+ uint16_t dev_id = xe_dev_id(fd);
+
+ igt_require_f(IS_CRESCENTISLAND(dev_id),
+ "This test requires CRI GPU, but found device ID 0x%04x\n", dev_id);
+}
+
static void inject_error(const char *injection, struct xe_mmio *mmio, int fd)
{
igt_info("Starting Error Injection test: %s\n", injection);
@@ -567,6 +576,11 @@ int igt_main()
igt_fixture() {
fd = drm_open_driver(DRIVER_XE);
igt_require(igt_debugfs_exists(fd, "forcewake_all", O_RDONLY));
+ igt_require_cri(fd);
+ /*
+ * TODO: Add firmware query for error injection support.
+ * Should check: EOM (End of Manufacturing) status and error injection jumper state.
+ */
xe_mmio_access_init(fd, &mmio);
igt_require(xe_mmio_is_initialized(&mmio));
}
--
2.34.1
prev parent reply other threads:[~2026-08-20 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 12:15 [PATCH v2 0/8] Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 1/8] lib/igt_drm_netlink: Introduce DRM RAS Generic Netlink interface Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 2/8] lib/igt_drm_netlink: add get_error_counter support Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 3/8] lib/igt_drm_netlink: add get_error_threshold command support Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 4/8] lib/igt_drm_netlink: add set_error_threshold " Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 5/8] tests/intel/xe_err_injection: Add GT UC Unicast GAM Walker Command Parity Error Injection Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 6/8] lib/igt_drm_netlink: add event notify subscription and event wait support Ravi Kishore Koppuravuri
2026-08-20 12:15 ` [PATCH v2 7/8] tests/intel/xe_err_injection: Add tests for L2 bank Corr err threshold scenarios Ravi Kishore Koppuravuri
2026-08-20 12:16 ` Ravi Kishore Koppuravuri [this message]
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=20260820121600.75052-9-ravi.kishore.koppuravuri@intel.com \
--to=ravi.kishore.koppuravuri@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=soham.purkait@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