From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: igt-dev@lists.freedesktop.org,
Petri Latvala <adrinael@adrinael.net>,
Arkadiusz Hiler <arek@hiler.eu>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
Bhanuprakash Modem <bhanuprakash.modem@gmail.com>
Cc: "Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
kernel@collabora.com
Subject: [PATCH v2 0/3] Test panthor sparse mappings
Date: Fri, 8 May 2026 18:25:32 +0100 [thread overview]
Message-ID: <20260508172537.3456595-1-adrian.larumbe@collabora.com> (raw)
This patch series adds IGT tests to validate Panthor's sparse mappings
functionality. They are meant to support sparse bindings in Vulkan, but we
found it necessary to test it separately to make sure all corner remap and
unmap cases intersecting with sparse VA's are covered.
Link to the previous revision can be found at [1].
Kernel patches necessary to test the functionality herein can be found at [2]
Changelog:
v2:
- Reformated DRM uAPI update commit so that it meets the usual IGT convention.
- Renamed panthor_vm_repeat.c to panthor_vm_sparse.c to reflect changes in interface naming.
- Deleted test that submits job to the GPU targeting bound addresses because sparse mappings
no longer require a user-created BO.
- Changed interfaces and sparse mapping sequence in the tests to reflect the changes above.
[1] https://lore.kernel.org/igt-dev/20260313175908.1752151-1-adrian.larumbe@collabora.com
[2] https://lore.kernel.org/dri-devel/20260507214939.2852489-1-adrian.larumbe@collabora.com
Adrián Larumbe (3):
drm-uapi/panthor: sync with kernel 5731bca6a656
panthor: Add IGT library helper for Panthor sparse mappings
tests/panthor: Add Panthor sparse VM_BIND tests
include/drm-uapi/panthor_drm.h | 246 ++++++++++++++++++++++-
lib/igt_panthor.h | 9 +
tests/panthor/meson.build | 1 +
tests/panthor/panthor_vm_sparse.c | 316 ++++++++++++++++++++++++++++++
4 files changed, 566 insertions(+), 6 deletions(-)
create mode 100644 tests/panthor/panthor_vm_sparse.c
base-commit: 529869b7d0fba64ed67819111079ff269bc8159a
--
2.53.0
next reply other threads:[~2026-05-08 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 17:25 Adrián Larumbe [this message]
2026-05-08 17:25 ` [PATCH v2 1/3] drm-uapi/panthor: sync with kernel 5731bca6a656 Adrián Larumbe
2026-05-13 14:04 ` Kamil Konieczny
2026-05-08 17:25 ` [PATCH v2 2/3] panthor: Add IGT library helper for Panthor sparse mappings Adrián Larumbe
2026-05-13 14:00 ` Kamil Konieczny
2026-05-08 17:25 ` [PATCH v2 3/3] tests/panthor: Add Panthor sparse VM_BIND tests Adrián Larumbe
2026-05-13 13:54 ` Kamil Konieczny
2026-05-13 14:48 ` Kamil Konieczny
2026-05-09 0:55 ` ✓ i915.CI.BAT: success for Test panthor sparse mappings Patchwork
2026-05-09 1:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-09 14:25 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-10 2:32 ` ✓ i915.CI.Full: success " 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=20260508172537.3456595-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=adrinael@adrinael.net \
--cc=arek@hiler.eu \
--cc=bhanuprakash.modem@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=steven.price@arm.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