From: Harish Chegondi <harish.chegondi@intel.com>
To: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
Cc: <igt-dev@lists.freedesktop.org>, <riana.tauro@intel.com>,
<anshuman.gupta@intel.com>, <mallesh.koujalagi@intel.com>,
<raag.jadav@intel.com>
Subject: Re: [PATCH 8/8] tests/intel/xe_err_injection: add CRI GPU requirement check
Date: Thu, 6 Aug 2026 17:06:15 -0700 [thread overview]
Message-ID: <anUhdyJ_WZmvRDNL@intel.com> (raw)
In-Reply-To: <20260729121959.603890-9-ravi.kishore.koppuravuri@intel.com>
On Wed, Jul 29, 2026 at 05:49:59PM +0530, Ravi Kishore Koppuravuri wrote:
> 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 0303f4a56..4df4589b3 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"
>
> @@ -508,6 +509,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);
> @@ -531,6 +540,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);
Instead of a separate function, you can just use the igt_require_f(IS_CRESCENTISLAND(dev_id),..) here
> + /*
> + * 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
>
I think this patch should be merged into the patch 5/8:
Add GT UC Unicast GAM Walker Command Parity Error Injection
Since, these error injection tests are run only on CRI as of now, this
patch can be squashed into 5/8
prev parent reply other threads:[~2026-08-07 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 12:19 [PATCH 0/8] Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support Ravi Kishore Koppuravuri
2026-07-29 12:19 ` [PATCH 1/8] lib/igt_drm_netlink: Introduce DRM RAS Generic Netlink interface Ravi Kishore Koppuravuri
2026-08-06 23:45 ` Harish Chegondi
2026-08-11 8:02 ` Koppuravuri, Ravi Kishore
2026-07-29 12:19 ` [PATCH 2/8] lib/igt_drm_netlink: add get_error_counter support Ravi Kishore Koppuravuri
2026-07-29 12:19 ` [PATCH 3/8] lib/igt_drm_netlink: add get_error_threshold command support Ravi Kishore Koppuravuri
2026-08-07 23:14 ` Harish Chegondi
2026-08-11 11:53 ` Koppuravuri, Ravi Kishore
2026-07-29 12:19 ` [PATCH 4/8] lib/igt_drm_netlink: add set_error_threshold " Ravi Kishore Koppuravuri
2026-08-07 23:21 ` Harish Chegondi
2026-08-11 11:47 ` Koppuravuri, Ravi Kishore
2026-07-29 12:19 ` [PATCH 5/8] tests/intel/xe_err_injection: Add GT UC Unicast GAM Walker Command Parity Error Injection Ravi Kishore Koppuravuri
2026-08-10 22:28 ` Harish Chegondi
2026-08-11 11:58 ` Koppuravuri, Ravi Kishore
2026-07-29 12:19 ` [PATCH 6/8] lib/igt_drm_netlink: add event notify subscription and event wait support Ravi Kishore Koppuravuri
2026-07-29 12:19 ` [PATCH 7/8] tests/intel/xe_err_injection: Add tests for L2 bank Corr err threshold scenarios Ravi Kishore Koppuravuri
2026-07-29 12:19 ` [PATCH 8/8] tests/intel/xe_err_injection: add CRI GPU requirement check Ravi Kishore Koppuravuri
2026-08-07 0:06 ` Harish Chegondi [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=anUhdyJ_WZmvRDNL@intel.com \
--to=harish.chegondi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@intel.com \
--cc=riana.tauro@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