[PATCH i-g-t v5 17/24] tests: Introduce Synchronization subcategory

Katarzyna Piecielska katarzyna.piecielska at intel.com
Thu Mar 21 15:38:40 UTC 2024


DRM and i915 subcategories seems to be too wide and general. Let's use
Synchronization subcategory.

v2: Make Sub-category/Functionality/Feature unique values. (Kamil)

Signed-off-by: Katarzyna Piecielska <katarzyna.piecielska at intel.com>
Cc: Kamil Konieczny <kamil.konieczny at linux.intel.com>
Cc: Mauro Carvalho Chehab <mauro.chehab at linux.intel.com>
Reviewed-by: Mauro Carvalho Chehab <mauro.chehab at linux.intel.com>
---
 tests/intel/gem_sync.c | 28 ++++++++++++++--------------
 tests/sw_sync.c        |  1 +
 tests/syncobj_basic.c  |  6 +++---
 3 files changed, 18 insertions(+), 17 deletions(-)

diff --git a/tests/intel/gem_sync.c b/tests/intel/gem_sync.c
index d3de2e77e..eee13789e 100644
--- a/tests/intel/gem_sync.c
+++ b/tests/intel/gem_sync.c
@@ -36,9 +36,9 @@
  * TEST: gem sync
  * Category: Infrastructure
  * Description: Basic check of ring<->ring write synchronisation.
- * Feature: synchronization
+ * Feature: synchronization feature
  * Functionality: semaphore
- * Sub-category: i915
+ * Sub-category: Synchronization
  * Test category: GEM_Legacy
  * Run type: FULL
  *
@@ -47,14 +47,14 @@
  *
  * SUBTEST: active-each
  * Description: Exercise waiting while keeping the GPU busy.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: active-wakeup
  * Description: Measure wakeup latency while also scheduling the next batch on each engine.
  *
  * SUBTEST: active-wakeup-each
  * Description: Measure wakeup latency while also scheduling the next batch.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: basic-all
  * Description: Basic test to wait upon a batch on all rings.
@@ -64,7 +64,7 @@
  * Description:
  *   Check synchronisation of ring.
  *   Exercise all physical engine selection and legacy rings
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  * Run type: BAT
  * Test category: MultiTile
  *
@@ -72,7 +72,7 @@
  * Description:
  *   Create race condition and see if we can catch interrupts.
  *   Basic check of ring to ring write synchronisation
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  * Test category: MultiTile
  *
  * SUBTEST: basic-store-all
@@ -82,7 +82,7 @@
  * Description:
  *   Check that store synchronisation works.
  *   Basic check of ring to ring write, store synchronisation
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  * Test category: MultiTile
  *
  * SUBTEST: default
@@ -93,7 +93,7 @@
  *
  * SUBTEST: double-wakeup-each
  * Description: Double stress test for nop + sync.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: forked
  * Description: Check synchronisation of ring with parallel executions on each engine.
@@ -105,7 +105,7 @@
  * Description:
  *   Forked variant of sync_ring, which checks synchronisation of ring with parallel
  *   executions.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: forked-store
  * Description: Check store synchronisation works with parallel multiple executions on each engine.
@@ -115,14 +115,14 @@
  *
  * SUBTEST: forked-store-each
  * Description: Forked variant of store_ring, check if parallel store synchronisation works.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: forked-switch
  * Description: Check sync after context switch parallelly on each engine.
  *
  * SUBTEST: forked-switch-each
  * Description: Check sync after context switch parallelly.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: idle
  * Description: Exercise and measure idle requests on each engine.
@@ -161,7 +161,7 @@
  *
  * SUBTEST: legacy-switch
  * Description: Check sync after context switch for each legacy engine.
- * Feature: synchronization
+ * Feature: synchronization feature
  * Run type: FULL
  *
  * SUBTEST: legacy-wakeup
@@ -189,7 +189,7 @@
  *
  * SUBTEST: switch-each
  * Description: Check sync after context switch.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  *
  * SUBTEST: wait-all
  * Description: Extended version of existing basic-all test.
@@ -199,7 +199,7 @@
  *
  * SUBTEST: wakeup-each
  * Description: Stress test for nop + sync.
- * Feature: multitile, synchronization
+ * Feature: multitile, synchronization feature
  */
 
 #define MAX_PRIO I915_CONTEXT_MAX_USER_PRIORITY
diff --git a/tests/sw_sync.c b/tests/sw_sync.c
index a276c4a22..8ea3dbe6c 100644
--- a/tests/sw_sync.c
+++ b/tests/sw_sync.c
@@ -44,6 +44,7 @@
  * Description: Test SW Sync Framework
  * Feature: semaphore
  * Functionality: sw sync framework
+ * Run type: FULL
  * Sub-category: uapi
  * Test category: GEM_Legacy
  *
diff --git a/tests/syncobj_basic.c b/tests/syncobj_basic.c
index f079baf09..18bef7c5c 100644
--- a/tests/syncobj_basic.c
+++ b/tests/syncobj_basic.c
@@ -30,10 +30,10 @@
  * TEST: syncobj basic
  * Category: Infrastructure
  * Description: Basic check for drm sync objects.
- * Feature: synchronization
- * Functionality: semaphore
+ * Feature: semaphore
+ * Functionality: drm sync object
  * Run type: FULL
- * Sub-category: DRM
+ * Sub-category: Synchronization
  * Test category: GEM_Legacy
  *
  * SUBTEST: bad-create-flags
-- 
2.34.1



More information about the igt-dev mailing list