public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Aditya Chauhan <aditya.chauhan@intel.com>
To: ramadevi.gandi@intel.com, himanshu.girotra@intel.com,
	swati2.sharma@intel.com, kamil.konieczny@intel.com,
	igt-dev@lists.freedesktop.org
Subject: [PATCH v4 i-g-t 1/2] intel-ci: Add NVL core blocklist
Date: Fri, 13 Mar 2026 18:04:58 +0530	[thread overview]
Message-ID: <20260313123459.64815-2-aditya.chauhan@intel.com> (raw)
In-Reply-To: <20260313123459.64815-1-aditya.chauhan@intel.com>

Introduce core blocklist for the NVL platform containing
NVL-specific core test exclusions. Also add this blocklist file
to meson.build so that this can be used in execution.

v2: Make commit message more descriptive (Swati Sharma)
v3:
 - Use correct subject (intel-ci) (Swati Sharma)
 - Add blocklist in alphabetical order in meson.build (Swati Sharma)
v4: Make comments more explanatory (Swati Sharma)

Signed-off-by: Aditya Chauhan <aditya.chauhan@intel.com>
---
 tests/intel-ci/meson.build               |  1 +
 tests/intel-ci/xe.nvl.core.blocklist.txt | 97 ++++++++++++++++++++++++
 2 files changed, 98 insertions(+)
 create mode 100644 tests/intel-ci/xe.nvl.core.blocklist.txt

diff --git a/tests/intel-ci/meson.build b/tests/intel-ci/meson.build
index cf0023c63..3c7fa28b7 100644
--- a/tests/intel-ci/meson.build
+++ b/tests/intel-ci/meson.build
@@ -23,6 +23,7 @@ intelci_files = [
   'xe.lnl.display.blocklist.txt',
   'xe.lnl.eudebug.blocklist.txt',
   'xe.multigpu.blocklist.txt',
+  'xe.nvl.core.blocklist.txt',
   'xe.ptl.core.blocklist.txt',
   'xe.ptl.display.blocklist.txt',
   'xe.sriov-vf.blocklist.txt',
diff --git a/tests/intel-ci/xe.nvl.core.blocklist.txt b/tests/intel-ci/xe.nvl.core.blocklist.txt
new file mode 100644
index 000000000..0f9750961
--- /dev/null
+++ b/tests/intel-ci/xe.nvl.core.blocklist.txt
@@ -0,0 +1,97 @@
+##################################################################
+# SR-IOV/IOV tests are not applicable for native
+# configuration and will be run under its separate configuration
+##################################################################
+igt@.*iov.*
+##################################################################
+# All Display related tests are being run under
+# separate display configurations
+##################################################################
+igt@.*kms.*
+igt@testdisplay
+igt@xe_pat@display-vs-wb-transient
+igt@fbdev@.*
+##################################################################
+# Valid skip: NVL is an integrated GPU and does not have
+# dedicated VRAM. Tests requiring device-local memory (VRAM),
+# small-BAR configurations, or VRAM eviction are not applicable.
+##################################################################
+igt@xe_mmap@vram$
+igt@xe_mmap@small-bar
+igt@xe_noexec_ping_pong
+igt@xe_create@create-big-vram
+igt@xe_evict.*
+igt@xe_pm@d3hot-mmap-vram
+igt@xe_eudebug_online@writes-caching-(?!sram-bb-sram-target-sram).*
+igt@xe_compute_preempt@.*vram.*
+igt@xe_vm@out-of-memory
+##################################################################
+# Valid skip: PAT index tests targeting older/different platforms
+# These PAT (Page Attribute Table) index subtests validate
+# platform-specific memory attribute encodings that are only
+# defined for their respective GPU generations
+# like ADL, MTL, LNL, BMG, PVC.
+# NVL uses its own PAT encoding; running these tests would
+# produce incorrect results or false failures.
+##################################################################
+igt@xe_pat@pat-index-xehpc
+igt@xe_pat@pat-index-xelp
+igt@xe_pat@pat-index-xelpg
+igt@xe_media_fill@media-fill
+igt@xe_pat@pat-index-xe2
+##################################################################
+# Valid Skip: Tests requiring multiple CCS (Compute Command
+# Streamers) engines — NVL exposes only a single CCS engine.
+##################################################################
+igt@xe_compute@ccs-mode-basic
+igt@xe_compute@ccs-mode-compute-kernel
+igt@xe_compute@eu-busy-10s
+##################################################################
+# Valid skip: Features / hardware blocks not present on NVL
+#   - xe_huc_copy@huc_copy: HuC (HEVC µController) firmware is
+#     not loaded/present on NVL; HuC copy operations will fail.
+#   - xe_exec_balancer@.*: Virtual engine / load balancer tests
+#     require multiple physical engines of the same class for
+#     balancing, which NVL does not expose.
+#   - xe_oa@oa-tlb-invalidate: OA TLB invalidation test relies
+#     on a specific OA unit configuration not present on NVL.
+#   - xe_pxp@.*: PXP (Protected Xe Path) content protection
+#     requires a TEE (Trusted Execution Environment) and
+#     associated firmware, which NVL does not support.
+#   - xe_exec_system_allocator@.*: System allocator execution
+#     tests depend on hardware features (e.g., SVM/USM page
+#     fault handling) not enabled on NVL yet.
+##################################################################
+igt@xe_huc_copy@huc_copy
+igt@xe_exec_balancer@.*
+igt@xe_oa@oa-tlb-invalidate
+igt@xe_pxp@.*
+igt@xe_exec_system_allocator@.*
+##################################################################
+# Valid skip: test applicable only for i2c capable systems
+##################################################################
+igt@xe_pm@d3hot-i2c
+##################################################################
+# Valid skip: multigpu/multitile tests are not supported on NVL
+##################################################################
+igt@.*@.*multigpu.*
+igt@xe_peer2peer@.*
+igt@.*@.*tiles
+##################################################################
+# Valid skip: Not Applicable for iGPUs
+##################################################################
+igt@intel_hwmon@.*
+igt@xe_mmap@pci-membarrier.*
+igt@xe_configfs@survivability-mode
+igt@xe_survivability@.*
+##################################################################
+# Valid skip: EU debugger and SIP (System Interrupt Protocol)
+# support is not yet available in the kernel for NVL. These tests
+# will be re-enabled once the required kernel enablement lands.
+##################################################################
+igt@xe_eudebug@.*
+igt@xe_eudebug_online@.*
+igt@xe_exec_sip@.*
+igt@xe_exec_sip_eudebug@.*
+igt@xe_live_ktest@xe_eudebug
+##################################################################
-- 
2.34.1


  reply	other threads:[~2026-03-13 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 12:34 [PATCH v4 i-g-t 0/2] intel-ci: Add NVL display and core blocklists Aditya Chauhan
2026-03-13 12:34 ` Aditya Chauhan [this message]
2026-03-13 14:43   ` [PATCH v4 i-g-t 1/2] intel-ci: Add NVL core blocklist Kamil Konieczny
2026-03-16 12:44     ` Kamil Konieczny
2026-03-16 13:37   ` Sharma, Swati2
2026-03-13 12:34 ` [PATCH v4 i-g-t 2/2] intel-ci: Add NVL Display blocklist to meson.build Aditya Chauhan
2026-03-16 13:38   ` Sharma, Swati2
2026-03-13 15:12 ` ✓ Xe.CI.BAT: success for intel-ci: Add NVL display and core blocklists (rev2) Patchwork
2026-03-13 15:28 ` ✓ i915.CI.BAT: " Patchwork
2026-03-14 17:50 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-14 18:02 ` ✗ i915.CI.Full: failure " 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=20260313123459.64815-2-aditya.chauhan@intel.com \
    --to=aditya.chauhan@intel.com \
    --cc=himanshu.girotra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@intel.com \
    --cc=ramadevi.gandi@intel.com \
    --cc=swati2.sharma@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