From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"K V P, Satyanarayana" <satyanarayana.k.v.p@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Dugast, Francois" <francois.dugast@intel.com>,
"Harrison, John C" <john.c.harrison@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault
Date: Mon, 2 Jun 2025 15:00:42 +0200 [thread overview]
Message-ID: <7aa19e84-6bd4-4e6c-a70e-242cf96a102a@intel.com> (raw)
In-Reply-To: <CH0PR11MB54442A56220EDDF9DB18A52DE566A@CH0PR11MB5444.namprd11.prod.outlook.com>
On 29.05.2025 23:48, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Wajdeczko, Michal <Michal.Wajdeczko@intel.com>
> Sent: Thursday, May 29, 2025 1:14 PM
> To: K V P, Satyanarayana <satyanarayana.k.v.p@intel.com>; igt-dev@lists.freedesktop.org; Ceraolo Spurio, Daniele <daniele.ceraolospurio@intel.com>
> Cc: Dugast, Francois <francois.dugast@intel.com>; Cavitt, Jonathan <jonathan.cavitt@intel.com>; Harrison, John C <john.c.harrison@intel.com>
> Subject: Re: [PATCH i-g-t] tests/intel/xe_fault_injection: Ignore all errors while injecting fault
>> 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*
>
> The regex for that would probably look something like:
>
> igt_emit_ignore_dmesg_regex("^((?!ERROR).)*$");
>
> The above regex should filter out all CI warnings that don't contain errors.
I would prefer regex to match as much as possible and thus include DUT
BDF to avoid filtering out too much
>
>>
>> and we want to catch/report all warn/WARN/BUG without just relying on
>> taint (and WARN will also catch our xe_asserts)
>
> If you also want to catch WARNs and BUGs, then the filter would look
> more like:
we don't expect any WARNs or BUGs so we do not want them to be filtered
out, but highlighted instead
>
> igt_emit_ignore_dmesg_regex("^((?!ERROR|WARN|BUG).)*$");
>
> Would either of these be more amenable, Michal?
> -Jonathan Cavitt
>
>>
>>
next prev parent reply other threads:[~2025-06-02 13:00 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 ` [PATCH i-g-t] " Michal Wajdeczko
2025-05-29 21:48 ` Cavitt, Jonathan
2025-05-30 17:39 ` Kamil Konieczny
2025-06-02 13:00 ` Michal Wajdeczko [this message]
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=7aa19e84-6bd4-4e6c-a70e-242cf96a102a@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=rodrigo.vivi@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