Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
	Francois Dugast <francois.dugast@intel.com>,
	Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Subject: [PATCH i-g-t 0/2] xe_fault_injection: Improve probe fault injection handling
Date: Thu, 17 Apr 2025 15:13:10 +0200	[thread overview]
Message-ID: <20250417131312.1016503-1-marcin.bernatowicz@linux.intel.com> (raw)

This patch series improves fault injection test coverage in the
xe_fault_injection test by decoupling error checking from the fault
injection helper and making tests aware of Virtual Function (VF) contexts.

Patch 1 modifies the `inject_fault_probe()` helper to return the result
of the probe instead of asserting internally. This change allows callers
to determine whether an assertion is needed, and enables more flexible
handling of fault injection scenarios.

Patch 2 updates the "inject-fault-probe-function*" tests to be VF-aware.
Some functions listed for probe fault injection are only expected to fail
on Physical Functions (PF), and may not be invoked at all on VFs. These
functions are now marked with a `pf_only` flag and handled appropriately
at runtime based on device type.

Together, these changes enable more accurate and robust testing of fault
injection across both PF and VF environments, avoiding false failures on
VF.

Cc: Francois Dugast <francois.dugast@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>

Marcin Bernatowicz (2):
  tests/intel/xe_fault_injection: Return probe result from
    inject_fault_probe
  tests/intel/xe_fault_injection: Make inject-fault-probe-function*
    tests VF-aware

 tests/intel/xe_fault_injection.c | 30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

-- 
2.31.1


             reply	other threads:[~2025-04-17 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 13:13 Marcin Bernatowicz [this message]
2025-04-17 13:13 ` [PATCH i-g-t 1/2] tests/intel/xe_fault_injection: Return probe result from inject_fault_probe Marcin Bernatowicz
2025-04-17 13:13 ` [PATCH i-g-t 2/2] tests/intel/xe_fault_injection: Make inject-fault-probe-function* tests VF-aware Marcin Bernatowicz
2025-04-17 14:51 ` ✗ Xe.CI.BAT: failure for xe_fault_injection: Improve probe fault injection handling Patchwork
2025-04-25 10:05   ` Bernatowicz, Marcin
2025-04-17 14:58 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-18  2:57 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-18  7:08 ` ✗ Xe.CI.Full: " Patchwork
2025-04-25 10:07   ` Bernatowicz, Marcin

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=20250417131312.1016503-1-marcin.bernatowicz@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=francois.dugast@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=satyanarayana.k.v.p@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