From: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Subject: [PATCH i-g-t v4 0/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv
Date: Wed, 22 Jan 2025 13:08:06 +0530 [thread overview]
Message-ID: <20250122073808.16288-1-satyanarayana.k.v.p@intel.com> (raw)
Use the kernel fault injection infrastructure to test error handling of xe
at probe time when executing xe_guc_mmio_send_recv() and at enabling of VFs
stage when executing xe_guc_ct_send_recv().
Error can be injected using:
igt@xe_fault_injection@inject-fault-probe-function-xe_guc_mmio_send_recv
igt@xe_fault_injection@enable-vfs-fail-xe_guc_ct_send_recv
Satyanarayana K V P (2):
tests/intel/xe_fault_injection: Inject errors during
xe_guc_mmio_send_recv
tests/intel/xe_fault_injection: Inject errors during
xe_guc_ct_send_recv
tests/intel/xe_fault_injection.c | 64 ++++++++++++++++++++++++++++++++
1 file changed, 64 insertions(+)
--
2.35.3
next reply other threads:[~2025-01-22 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 7:38 Satyanarayana K V P [this message]
2025-01-22 7:38 ` [PATCH i-g-t v4 1/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_mmio_send_recv Satyanarayana K V P
2025-01-22 14:54 ` Michal Wajdeczko
2025-01-22 7:38 ` [PATCH i-g-t v4 2/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv Satyanarayana K V P
2025-01-22 15:22 ` Michal Wajdeczko
2025-01-22 10:44 ` ✓ i915.CI.BAT: success for tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv (rev4) Patchwork
2025-01-22 11:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-22 21:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-23 15:00 ` ✗ 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=20250122073808.16288-1-satyanarayana.k.v.p@intel.com \
--to=satyanarayana.k.v.p@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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