From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: adam.miszczak@linux.intel.com, jakub1.kolakowski@intel.com,
lukasz.laguna@intel.com,
Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Subject: [PATCH v2 i-g-t 0/6] Add SR-IOV exit-handler-based cleanup
Date: Mon, 15 Jun 2026 12:32:14 +0200 [thread overview]
Message-ID: <20260615103220.281656-1-marcin.bernatowicz@linux.intel.com> (raw)
This series adds SR-IOV exit-handler-based cleanup in SR-IOV test paths to
improve recovery when a test exits unexpectedly (for example, via SIGQUIT
from igt_runner), while preserving strict explicit teardown
in normal fixture flow.
Goal: keep PF state restoration robust across failures:
- disable VFs on exit
- restore sriov_drivers_autoprobe state
- restore XE SR-IOV admin scheduling defaults when modified by the test
- keep explicit fixture teardown authoritative, and clear the exit handler
only after teardown succeeds
Series is split by teardown pattern to keep review and maintenance simple:
- no-callback users
- XE admin callback users
- FLR-specific callback users, plus helper refactor to reduce duplication
v2: No need for restore_autoprobe option,
just always restore on exit. (Lukasz)
Marcin Bernatowicz (6):
lib/igt_device_sriov: Add generic SR-IOV exit cleanup helper
lib/xe/xe_sriov_admin: Add SR-IOV admin exit cleanup restore helper
tests/sriov_basic: Arm SR-IOV exit cleanup
tests/xe: Arm SR-IOV exit cleanup
tests/xe: Arm SR-IOV exit cleanup with callback
tests/intel/xe_sriov_flr: Arm SR-IOV exit cleanup
lib/igt_sriov_device.c | 91 ++++++++++++++++++++++++
lib/igt_sriov_device.h | 5 ++
lib/xe/xe_sriov_admin.c | 21 ++++++
lib/xe/xe_sriov_admin.h | 2 +
tests/intel/xe_pmu.c | 4 ++
tests/intel/xe_sriov_admin.c | 4 ++
tests/intel/xe_sriov_auto_provisioning.c | 2 +
tests/intel/xe_sriov_flr.c | 42 ++++++++---
tests/intel/xe_sriov_scheduling.c | 4 ++
tests/intel/xe_sriov_vram.c | 2 +
tests/sriov_basic.c | 2 +
11 files changed, 170 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-15 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 10:32 Marcin Bernatowicz [this message]
2026-06-15 10:32 ` [PATCH v2 i-g-t 1/6] lib/igt_device_sriov: Add generic SR-IOV exit cleanup helper Marcin Bernatowicz
2026-06-15 10:32 ` [PATCH v2 i-g-t 2/6] lib/xe/xe_sriov_admin: Add SR-IOV admin exit cleanup restore helper Marcin Bernatowicz
2026-06-15 10:32 ` [PATCH v2 i-g-t 3/6] tests/sriov_basic: Arm SR-IOV exit cleanup Marcin Bernatowicz
2026-06-15 10:32 ` [PATCH v2 i-g-t 4/6] tests/xe: " Marcin Bernatowicz
2026-06-15 10:32 ` [PATCH v2 i-g-t 5/6] tests/xe: Arm SR-IOV exit cleanup with callback Marcin Bernatowicz
2026-06-15 10:32 ` [PATCH v2 i-g-t 6/6] tests/intel/xe_sriov_flr: Arm SR-IOV exit cleanup Marcin Bernatowicz
2026-06-15 17:36 ` ✓ i915.CI.BAT: success for Add SR-IOV exit-handler-based cleanup (rev2) Patchwork
2026-06-15 17:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-15 18:44 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-16 1:02 ` ✗ 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=20260615103220.281656-1-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=lukasz.laguna@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.