All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Laguna <lukasz.laguna@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: marcin.bernatowicz@intel.com, piotr.piorkowski@intel.com
Subject: [PATCH 0/2] tests/intel/xe_sriov_ggtt: Add test checking GGTT accesses
Date: Tue,  4 Aug 2026 09:24:05 +0200	[thread overview]
Message-ID: <20260804072407.1090889-1-lukasz.laguna@intel.com> (raw)

Add a test validating PTE ownership, accessibility, and modifiability
by PF and VFs.

The following scenarios are covered:
- pf-check-vfs-ids: verify VF ID assignment for each VF GGTT range,
- pf-check-vfs-pte: verify PF modifiability of VF PTEs,
- vfs-check-own-pte: verify VF modifiability of its own PTEs,
- vfs-check-other-vfs-pte: verify VF can't access other VFs PTEs,
- vfs-check-pf-pte: verify VF can't access PF PTEs

Lukasz Laguna (1):
  intel-ci: Block igt@xe_sriov_ggtt.*

Piotr Piórkowski (1):
  tests/intel/xe_sriov_ggtt: Add test checking GGTT accesses

 lib/xe/xe_ggtt.h                |   7 +
 tests/intel-ci/xe.blocklist.txt |   4 +
 tests/intel/xe_sriov_ggtt.c     | 757 ++++++++++++++++++++++++++++++++
 tests/meson.build               |   1 +
 4 files changed, 769 insertions(+)
 create mode 100644 tests/intel/xe_sriov_ggtt.c

-- 
2.43.0


             reply	other threads:[~2026-08-04  7:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  7:24 Lukasz Laguna [this message]
2026-08-04  7:24 ` [PATCH 1/2] tests/intel/xe_sriov_ggtt: Add test checking GGTT accesses Lukasz Laguna
2026-08-18 13:45   ` Bernatowicz, Marcin
2026-08-04  7:24 ` [PATCH 2/2] intel-ci: Block igt@xe_sriov_ggtt.* Lukasz Laguna
2026-08-18 13:45   ` Bernatowicz, Marcin
2026-08-05  4:09 ` ✓ Xe.CI.BAT: success for tests/intel/xe_sriov_ggtt: Add test checking GGTT accesses Patchwork
2026-08-05  4:30 ` ✓ i915.CI.BAT: " Patchwork
2026-08-05  9:28 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-05 19:38 ` ✗ 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=20260804072407.1090889-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.