Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Miszczak <adam.miszczak@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: tomasz.lis@intel.com, marcin.bernatowicz@linux.intel.com,
	michal.wajdeczko@intel.com, lukasz.laguna@intel.com,
	jakub1.kolakowski@intel.com, satyanarayana.k.v.p@intel.com
Subject: [PATCH i-g-t 0/2] Add SR-IOV simplified VF migration test
Date: Wed, 19 Feb 2025 11:25:32 +0100	[thread overview]
Message-ID: <20250219102534.2630181-1-adam.miszczak@linux.intel.com> (raw)

New test validates simplified (a.k.a fake) VF migration scenario,
that doesn't require VM and VFIO driver support, as it relies on
PF and VF driver interfaces.
Test exercise possiblity to restore previously saved GuC state,
cleared during VF states transitions and reset.
Setup involves VF(s) provisioning (either auto or manual), enablement
and driver probe.
Additionally, runtime power management is disabled to prevent VF suspend.
VF run state (pause-resume) is controlled to put VF in a state allowing
to perform save/restore operations. GuC state as well as GGTT and LMEM
raw data is read via relevant debugfs attributes for later restore.
VF health in pre- and post-migration phase is verified by running
simple workload.

SRIOV debugfs library functions added to support tested scenario:
- send VF control commands
- get/set GuC state, GTTT and LMEM data
- trigger GGTT relocation

Note, test currently requires xe driver built with SRIOV debug flag:
CONFIG_DRM_XE_DEBUG_SRIOV=y

Cc: Tomasz Lis <tomasz.lis@intel.com>
Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>

Adam Miszczak (2):
  lib/xe/xe_sriov_debugfs: Add VF save/restore related functions
  tests/xe_sriov_migration: VF fake migration validation

 lib/xe/xe_sriov_debugfs.c        | 252 ++++++++++++++++++++++++++
 lib/xe/xe_sriov_debugfs.h        |  31 ++++
 tests/intel/xe_sriov_migration.c | 297 +++++++++++++++++++++++++++++++
 tests/meson.build                |   1 +
 4 files changed, 581 insertions(+)
 create mode 100644 tests/intel/xe_sriov_migration.c

-- 
2.39.1


             reply	other threads:[~2025-02-19 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 10:25 Adam Miszczak [this message]
2025-02-19 10:25 ` [PATCH i-g-t 1/2] lib/xe/xe_sriov_debugfs: Add VF save/restore related functions Adam Miszczak
2025-02-19 12:18   ` Michal Wajdeczko
2025-02-19 10:25 ` [PATCH i-g-t 2/2] tests/xe_sriov_migration: VF fake migration validation Adam Miszczak
2025-02-19 23:03 ` ✓ i915.CI.BAT: success for Add SR-IOV simplified VF migration test Patchwork
2025-02-19 23:17 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-20 11:00 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-20 20:52 ` ✗ Xe.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=20250219102534.2630181-1-adam.miszczak@linux.intel.com \
    --to=adam.miszczak@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=marcin.bernatowicz@linux.intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=satyanarayana.k.v.p@intel.com \
    --cc=tomasz.lis@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