Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dominik Karol Piątkowski" <dominik.karol.piatkowski@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
	"Dominik Karol Piątkowski" <dominik.karol.piatkowski@intel.com>
Subject: [PATCH v3 i-g-t 0/1] tests/intel/xe_exec_store: Introduce long-shader tests
Date: Wed,  4 Dec 2024 12:57:04 +0100	[thread overview]
Message-ID: <20241204115705.5455-1-dominik.karol.piatkowski@intel.com> (raw)

Introduce long-shader-bb-check test with dynamic subtests dependent on
available memory regions.

These dynamic subtests are core version of
xe_eudebug_online@writes-caching* tests.

Each dynamic subtest writes incrementing values to 2-page-long target
surface using long shader. The bb is searched for full shader, expecting
it to exist. The target surface is checked against written values. Each
dynamic subtest places bb and surface in different configuration of
memory regions in order to validate memory coherency.

v2:
- Change separate tests into dynamic subtests
- Don't use dangling hwe
- Use xe_get_memory_region_set and for_each_variation_r to iterate over
  all memory region pairs
v3:
- Add missing igt_collection_destroy

Signed-off-by: Dominik Karol Piątkowski <dominik.karol.piatkowski@intel.com>

Dominik Karol Piątkowski (1):
  tests/intel/xe_exec_store: Introduce long-shader tests

 tests/intel/xe_exec_store.c | 102 ++++++++++++++++++++++++++++++++++++
 1 file changed, 102 insertions(+)

-- 
2.34.1


             reply	other threads:[~2024-12-04 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 11:57 Dominik Karol Piątkowski [this message]
2024-12-04 11:57 ` [PATCH v3 i-g-t 1/1] tests/intel/xe_exec_store: Introduce long-shader tests Dominik Karol Piątkowski
2024-12-04 19:06 ` ✗ i915.CI.BAT: failure for " Patchwork
2024-12-04 19:09 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-04 23:18 ` ✗ Xe.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=20241204115705.5455-1-dominik.karol.piatkowski@intel.com \
    --to=dominik.karol.piatkowski@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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