From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
John Harrison <john.c.harrison@intel.com>
Subject: [PATCH 2/2] drm/xe/guc: Suppress Dead CTB Dump during fault injection tests
Date: Mon, 12 May 2025 18:19:47 +0200 [thread overview]
Message-ID: <20250512161947.128-3-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20250512161947.128-1-michal.wajdeczko@intel.com>
There is no point in generating a CTB dump due to a fault
injected by our tests, as it they will just stress our CI.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: John Harrison <john.c.harrison@intel.com>
---
drivers/gpu/drm/xe/xe_guc_ct.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index ff6edf1b14f4..c21dc88099ab 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -1964,6 +1964,10 @@ static void ct_dead_capture(struct xe_guc_ct *ct, struct guc_ctb *ctb, u32 reaso
if (ctb)
ctb->info.broken = true;
+ /* Skip dumps during internal testing */
+ if (xe_fault_injection_in_progress(ct_to_xe(ct)))
+ return;
+
/* Ignore further errors after the first dump until a reset */
if (ct->dead.reported)
return;
--
2.47.1
next prev parent reply other threads:[~2025-05-12 16:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 16:19 [PATCH 0/2] Suppress some dumps during fault injection tests Michal Wajdeczko
2025-05-12 16:19 ` [PATCH 1/2] drm/xe: Introduce flag to indicate possible fault injection Michal Wajdeczko
2025-05-12 18:36 ` John Harrison
2025-05-12 20:20 ` Michal Wajdeczko
2025-05-14 21:05 ` John Harrison
2025-05-15 10:25 ` Michal Wajdeczko
2025-05-21 21:15 ` John Harrison
2025-05-12 16:19 ` Michal Wajdeczko [this message]
2025-05-12 16:44 ` ✓ CI.Patch_applied: success for Suppress some dumps during fault injection tests Patchwork
2025-05-12 16:44 ` ✓ CI.checkpatch: " Patchwork
2025-05-12 16:45 ` ✓ CI.KUnit: " Patchwork
2025-05-12 16:55 ` ✗ CI.Build: failure " Patchwork
2025-05-13 11:09 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-13 11:09 ` ✓ CI.checkpatch: " Patchwork
2025-05-13 11:10 ` ✓ CI.KUnit: " Patchwork
2025-05-13 11:18 ` ✓ CI.Build: " Patchwork
2025-05-13 11:21 ` ✓ CI.Hooks: " Patchwork
2025-05-13 11:22 ` ✓ CI.checksparse: " Patchwork
2025-05-13 12:01 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-13 13:38 ` ✓ Xe.CI.Full: " Patchwork
2025-05-26 22:04 ` ✓ CI.Patch_applied: " Patchwork
2025-05-26 22:04 ` ✓ CI.checkpatch: " Patchwork
2025-05-26 22:05 ` ✓ CI.KUnit: " Patchwork
2025-05-26 22:15 ` ✓ CI.Build: " 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=20250512161947.128-3-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--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