Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: dominik.karol.piatkowski@intel.com, kamil.konieczny@intel.com
Subject: [PATCH i-g-t 1/1] tests/intel/xe_fault_injection: Inject errors for xe_hw_engine_class_to_str
Date: Fri,  4 Apr 2025 03:10:52 +0000	[thread overview]
Message-ID: <20250404031052.1848936-2-sobin.thomas@intel.com> (raw)
In-Reply-To: <20250404031052.1848936-1-sobin.thomas@intel.com>

Use the fault injection infrastructure to make targeted fault injection in
functions xe_hw_engine_class_to_str and check the error handling in the
xe_hw_engine_class_sysfs_init() so that more code paths involving error
handling is tested.

Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
---
 tests/intel/xe_fault_injection.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
index 24c114ba7..94c1bbf38 100644
--- a/tests/intel/xe_fault_injection.c
+++ b/tests/intel/xe_fault_injection.c
@@ -173,6 +173,7 @@ static void set_retval(const char function_name[], long long retval)
  * @xe_guc_ct_init:		xe_guc_ct_init
  * @xe_guc_log_init:		xe_guc_log_init
  * @xe_guc_relay_init:		xe_guc_relay_init
+ * @xe_hw_engine_class_to_str:	xe_hw_engine_class_to_str
  * @xe_mmio_probe_early:	xe_mmio_probe_early
  * @xe_pcode_probe_early:	xe_pcode_probe_early
  * @xe_pm_init_early:		xe_pm_init_early
@@ -388,6 +389,7 @@ igt_main
 		{ "xe_guc_ct_init" },
 		{ "xe_guc_log_init" },
 		{ "xe_guc_relay_init" },
+		{ "xe_hw_engine_class_to_str" },
 		{ "xe_mmio_probe_early" },
 		{ "xe_pcode_probe_early" },
 		{ "xe_pm_init_early" },
-- 
2.34.1


  reply	other threads:[~2025-04-04  3:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  3:10 [PATCH i-g-t 0/1] tests/intel/xe_fault_injection: Inject errors for xe_hw_engine_class_to_str Sobin Thomas
2025-04-04  3:10 ` Sobin Thomas [this message]
2025-04-04  5:06   ` [PATCH i-g-t 1/1] " Dandamudi, Priyanka
2025-04-04  7:40     ` Dandamudi, Priyanka
2025-04-04  5:03 ` ✓ i915.CI.BAT: success for " Patchwork
2025-04-04  5:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-04  6:49 ` ✓ i915.CI.Full: " Patchwork
2025-04-04  7:18 ` ✗ i915.CI.BAT: failure for tests/intel/xe_fault_injection: Inject errors for xe_hw_engine_class_to_str (rev2) Patchwork
2025-04-04  7:23 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-04 13:00 ` ✗ Xe.CI.Full: failure for tests/intel/xe_fault_injection: Inject errors for xe_hw_engine_class_to_str Patchwork
2025-04-04 17:11 ` ✗ Xe.CI.Full: failure for tests/intel/xe_fault_injection: Inject errors for xe_hw_engine_class_to_str (rev2) 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=20250404031052.1848936-2-sobin.thomas@intel.com \
    --to=sobin.thomas@intel.com \
    --cc=dominik.karol.piatkowski@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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