From: Lukasz Laguna <lukasz.laguna@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: marcin.bernatowicz@intel.com, piotr.piorkowski@intel.com
Subject: [PATCH v2 0/3] tests/intel/xe_sriov_mmio_regs: Add tests to verify registers on VFs
Date: Mon, 7 Sep 2026 14:46:55 +0200 [thread overview]
Message-ID: <20260907124658.613244-1-lukasz.laguna@intel.com> (raw)
In case of SR-IOV, the VF has limited access to the registers. Let's add
tests to verify that the VF actually has access only to the allowed list
of registers, and verify that registers dedicated to VFs work properly.
Lukasz Laguna (2):
lib/igt_sriov_device: Add helper to get SR-IOV function name
intel-ci: Block igt@xe_sriov_mmio_regs.*
Piotr Piórkowski (1):
tests/intel/xe_sriov_mmio_regs: Add tests to verify registers on VFs
lib/igt_sriov_device.c | 23 ++
lib/igt_sriov_device.h | 1 +
tests/intel-ci/xe.blocklist.txt | 1 +
tests/intel/xe_sriov_mmio_regs.c | 408 +++++++++++++++++++++++++++++++
tests/meson.build | 1 +
5 files changed, 434 insertions(+)
create mode 100644 tests/intel/xe_sriov_mmio_regs.c
--
2.43.0
next reply other threads:[~2026-09-07 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 12:46 Lukasz Laguna [this message]
2026-09-07 12:46 ` [PATCH v2 1/3] lib/igt_sriov_device: Add helper to get SR-IOV function name Lukasz Laguna
2026-09-08 13:16 ` Bernatowicz, Marcin
2026-09-07 12:46 ` [PATCH v2 2/3] tests/intel/xe_sriov_mmio_regs: Add tests to verify registers on VFs Lukasz Laguna
2026-09-10 10:26 ` Bernatowicz, Marcin
2026-09-07 12:46 ` [PATCH v2 3/3] intel-ci: Block igt@xe_sriov_mmio_regs.* Lukasz Laguna
2026-09-10 10:27 ` Bernatowicz, Marcin
2026-09-07 17:15 ` ✓ Xe.CI.BAT: success for tests/intel/xe_sriov_mmio_regs: Add tests to verify registers on VFs (rev2) Patchwork
2026-09-07 17:51 ` ✓ i915.CI.BAT: " Patchwork
2026-09-07 21:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-08 0:07 ` ✗ i915.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=20260907124658.613244-1-lukasz.laguna@intel.com \
--to=lukasz.laguna@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=marcin.bernatowicz@intel.com \
--cc=piotr.piorkowski@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