From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
igt-dev@lists.freedesktop.org,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
John Harrison <John.C.Harrison@Intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault
Date: Thu, 29 May 2025 22:14:03 +0200 [thread overview]
Message-ID: <bafb3f48-e1bb-4ed4-8419-dd5e85875795@intel.com> (raw)
In-Reply-To: <20250529133132.29912-1-satyanarayana.k.v.p@intel.com>
On 29.05.2025 15:31, Satyanarayana K V P wrote:
> Currently, numerous fault messages have been included in the dmesg ignore list,
> and this list continues to expand. Each time a new fault injection point is
> introduced or a new feature is activated, additional fault messages appear,
> making it cumbersome to manage the dmesg ignore list.
>
> This new patch automatically ignores all error messages from dmesg, eliminating
> the need to add or maintain a dmesg ignore message list.
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> ---
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> ---
> tests/intel/xe_fault_injection.c | 35 +++++++-------------------------
> 1 file changed, 7 insertions(+), 28 deletions(-)
>
> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
> index f9bd5c761..0dffbe5da 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -64,30 +64,9 @@ static int fail_function_open(void)
> return debugfs_fail_function_dir_fd;
> }
>
> -static bool function_is_part_of_guc(const char function_name[])
> +static void ignore_faults_in_dmesg(void)
> {
> - return strstr(function_name, "_guc_") != NULL ||
> - strstr(function_name, "_uc_") != NULL ||
> - strstr(function_name, "_wopcm_") != NULL;
> -}
> -
> -static void ignore_faults_in_dmesg(const char function_name[])
> -{
> - /* Driver probe is expected to fail in all cases, so ignore in igt_runner */
> - char regex[1024] = "probe with driver xe failed with error -12";
> -
> - /*
> - * If GuC module fault is injected, GuC is expected to fail,
> - * so also ignore GuC init failures in igt_runner.
> - */
> - if (function_is_part_of_guc(function_name)) {
> - strcat(regex, "|GT[0-9a-fA-F]*: GuC init failed with -ENOMEM");
> - strcat(regex, "|GT[0-9a-fA-F]*: Failed to initialize uC .-ENOMEM");
> - strcat(regex, "|GT[0-9a-fA-F]*: Failed to enable GuC CT .-ENOMEM");
> - strcat(regex, "|GT[0-9a-fA-F]*: GuC PC query task state failed: -ENOMEM");
> - }
> -
> - igt_emit_ignore_dmesg_regex(regex);
> + igt_emit_ignore_dmesg_regex(".*");
that will filter out all messages, no?
maybe we should look for KERN_ERR level messages
if IGT can't filter by level then at least look for our errors:
xe 0000:00:02.0 [drm] *ERROR*
xe ... [drm] *ERROR*
[drm] *ERROR*
*ERROR*
and we want to catch/report all warn/WARN/BUG without just relying on
taint (and WARN will also catch our xe_asserts)
next prev parent reply other threads:[~2025-05-29 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 13:31 [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault Satyanarayana K V P
2025-05-29 14:22 ` Cavitt, Jonathan
2025-05-29 16:23 ` Daniele Ceraolo Spurio
2025-05-29 20:29 ` Michal Wajdeczko
2025-06-02 18:25 ` Daniele Ceraolo Spurio
2025-06-02 18:30 ` Cavitt, Jonathan
2025-06-02 20:31 ` Daniele Ceraolo Spurio
2025-06-02 21:09 ` Cavitt, Jonathan
2025-06-02 21:31 ` Lucas De Marchi
2025-05-29 18:40 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2025-05-29 20:14 ` Michal Wajdeczko [this message]
2025-05-29 21:48 ` [PATCH i-g-t] " Cavitt, Jonathan
2025-05-30 17:39 ` Kamil Konieczny
2025-06-02 13:00 ` Michal Wajdeczko
2025-06-02 15:17 ` Cavitt, Jonathan
2025-05-30 17:38 ` Kamil Konieczny
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=bafb3f48-e1bb-4ed4-8419-dd5e85875795@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=John.C.Harrison@Intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jonathan.cavitt@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