Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Purkait, Soham" <soham.purkait@intel.com>
To: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>,
	<igt-dev@lists.freedesktop.org>
Cc: Riana Tauro <riana.tauro@intel.com>,
	Anshuman Gupta <anshuman.gupta@intel.com>,
	Raag Jadav <raag.jadav@intel.com>,
	Badal Nilawar <badal.nilawar@intel.com>,
	Mallesh Koujalagi <mallesh.koujalagi@intel.com>,
	Harish Chegondi <harish.chegondi@intel.com>
Subject: Re: [PATCH v5 10/10] tests/intel/xe_err_injection: add CRI GPU requirement check
Date: Fri, 23 Oct 2026 14:44:08 +0530	[thread overview]
Message-ID: <fcdc4d07-ab2b-4d17-a6a5-6594313991f9@intel.com> (raw)
In-Reply-To: <20261013190651.897241-11-ravi.kishore.koppuravuri@intel.com>

Hi Ravi,

On 14-10-2026 00:36, Ravi Kishore Koppuravuri wrote:
> Add support to verify the CRI GPU and skips test gracefully
> on non-cri platforms
>
> Cc: Soham Purkait <soham.purkait@intel.com>
> Cc: Riana Tauro <riana.tauro@intel.com>
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Cc: Raag Jadav <raag.jadav@intel.com>
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> Cc: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
> Cc: Harish Chegondi <harish.chegondi@intel.com>
> Signed-off-by: Ravi Kishore Koppuravuri <ravi.kishore.koppuravuri@intel.com>
> ---
> v5: Renamed the CRI GPU check function
> ---
>   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 796b4d696..46d9f7f42 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_ras_nl.h"
> +#include "lib/intel_chipset.h"
>   #include "lib/intel_reg.h"
>   #include "lib/intel_compute.h"
>   
> @@ -597,6 +598,14 @@ static void test_l2_bank_single_corr_err_injection(struct xe_mmio *mmio, int fd)
>   	CLEANUP_ON_ERROR(ctx, fw_handle);
>   }
>   
> +static void require_cri_gpu(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);
> +}
> +
>   enum xe_err_injection_type {
>   	XE_ERR_INJ_GT_UC_WKR_CMD_PARITY,
>   	XE_ERR_INJ_GT_UC_WKR_CMD_PARITY_POST_RECOVERY_WL,
> @@ -647,6 +656,11 @@ int igt_main()
>   		fd = drm_open_driver(DRIVER_XE);
>   		igt_require_f(igt_debugfs_exists(fd, "forcewake_all", O_RDONLY),
>   			      "forcewake_all is not available in debugfs\n");
> +		require_cri_gpu(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_f(xe_mmio_is_initialized(&mmio),
>   			      "Failed to initialize Xe MMIO access\n");
LGTM
Reviewed-by: Soham Purkait <soham.purkait@intel.com>

Regards,
Soham

  reply	other threads:[~2026-10-23  9:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 19:06 [PATCH v5 00/10] Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support Ravi Kishore Koppuravuri
2026-10-13 19:06 ` [PATCH v5 01/10] drm-uapi/drm_ras: Sync with kernel b2207d4c4e84 Ravi Kishore Koppuravuri
2026-10-22 11:56   ` Purkait, Soham
2026-10-13 19:06 ` [PATCH v5 02/10] lib/meson: Add libnl dependencies for DRM RAS support Ravi Kishore Koppuravuri
2026-10-22 11:56   ` Purkait, Soham
2026-10-13 19:06 ` [PATCH v5 03/10] lib/igt_drm_netlink: Introduce DRM RAS Netlink interface library Ravi Kishore Koppuravuri
2026-10-22 12:04   ` Purkait, Soham
2026-10-13 19:06 ` [PATCH v5 04/10] lib/igt_drm_netlink: add get_error_counter support Ravi Kishore Koppuravuri
2026-10-22 12:40   ` Purkait, Soham
2026-10-13 19:06 ` [PATCH v5 05/10] lib/igt_drm_netlink: add get_error_threshold command support Ravi Kishore Koppuravuri
2026-10-13 19:06 ` [PATCH v5 06/10] lib/igt_drm_netlink: add set_error_threshold " Ravi Kishore Koppuravuri
2026-10-22 16:55   ` Purkait, Soham
2026-10-13 19:06 ` [PATCH v5 07/10] tests/intel/xe_err_injection: Add GT UC Unicast GAM Walker Command Parity Error Injection Ravi Kishore Koppuravuri
2026-10-22 17:41   ` Purkait, Soham
2026-10-23 14:42   ` Tauro, Riana
2026-10-13 19:06 ` [PATCH v5 08/10] lib/igt_drm_netlink: add event notify subscription and event wait support Ravi Kishore Koppuravuri
2026-10-22 19:31   ` Purkait, Soham
2026-10-23  7:26     ` Koppuravuri, Ravi Kishore
2026-10-13 19:06 ` [PATCH v5 09/10] tests/intel/xe_err_injection: Add tests for L2 bank Corr err threshold scenarios Ravi Kishore Koppuravuri
2026-10-13 19:06 ` [PATCH v5 10/10] tests/intel/xe_err_injection: add CRI GPU requirement check Ravi Kishore Koppuravuri
2026-10-23  9:14   ` Purkait, Soham [this message]
2026-10-14  1:28 ` ✓ i915.CI.BAT: success for Xe3P GPU Error Injection Test Suite with DRM RAS Netlink Support (rev8) Patchwork
2026-10-14  5:35 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-14 10:25 ` ✗ i915.CI.Full: failure " Patchwork
2026-10-14 20:18 ` ✗ Xe.CI.FULL: " Patchwork

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=fcdc4d07-ab2b-4d17-a6a5-6594313991f9@intel.com \
    --to=soham.purkait@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=harish.chegondi@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