From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>,
Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [PATCH v2] tests/intel/xe_fault_injection: Ignore expected errors
Date: Tue, 19 Nov 2024 09:31:28 -0500 [thread overview]
Message-ID: <b712815e-a709-4506-9a6c-9c267ad5367c@intel.com> (raw)
In-Reply-To: <20241115140243.sp72xvmr5nnpkwtc@kamilkon-desk.igk.intel.com>
On 2024-11-15 9:02 a.m., Kamil Konieczny wrote:
> Hi Dong,,
> On 2024-11-12 at 12:58:55 -0500, Dong, Zhanjun wrote:
>>
>>
>> On 2024-11-08 10:58 a.m., Kamil Konieczny wrote:
>>> Hi Jonathan,
>>> On 2024-11-07 at 19:59:59 +0000, Jonathan Cavitt wrote:
>>>> The following errors can be observed when running the xe_fault_injection
>>>> subtests:
>>>>
>>>> [drm] *ERROR* GT0: GuC init failed with -ENOMEM
>>>> [drm] *ERROR* GT0: Failed to initialize uC (-ENOMEM)
>>>> probe with driver xe failed with error -12
>>>>
>>>> Add these messages to the dmesg ignore regex to the applicable tests
>>>> (specifically, all tests for the last error, and all tests that target
>>>> GuC subsystems for the first two errors).
>>>>
>>>> v2:
>>>> - Fix and merge regex (Kamil)
>>>>
>>>> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3343
>>>> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
>>>> CC: Francois Dugast <francois.dugast@intel.com>
>>>> CC: Lucas De Marchi <lucas.demarchi@intel.com>
>>>> CC: Matthew Brost <matthew.brost@intel.com>
>>>> CC: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>>> CC: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>>> CC: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>>>> ---
>>>> tests/intel/xe_fault_injection.c | 25 +++++++++++++++++++++++++
>>>> 1 file changed, 25 insertions(+)
>>>>
>>>> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
>>>> index d1c8b25307..8b181808ed 100644
>>>> --- a/tests/intel/xe_fault_injection.c
>>>> +++ b/tests/intel/xe_fault_injection.c
>>>> @@ -30,6 +30,30 @@ enum injection_list_action {
>>>> INJECTION_LIST_REMOVE,
>>>> };
>>>> +static bool function_is_part_of_guc(char function_name[])
>>>> +{
>>>> + return strstr(function_name, "_guc_") != NULL ||
>>>> + strstr(function_name, "_uc_") != NULL ||
>>>> + strstr(function_name, "_wopcm_") != NULL;
>>>> +}
>>>> +
>>>> +static void ignore_faults_in_dmesg(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");
>> I see "." matches left parenthesis, why don't have another "." match for
>> right parenthesis? I mean it looks strange when compare regex string:
>> "GT[0-9a-fA-F]*: Failed to initialize uC .-ENOMEM"
>> vs
>> "GT0: Failed to initialize uC (-ENOMEM)"
>
> Because using '(' in regex is tricky, also if we ignore last char
> we could as well improve regex and just do not require it.
I see, my first impression is a missing character, as long as not the
case, I'm OK.
Regards,
Zhanjun Dong
>
> Regards,
> Kamil
>
>>
>> Regards,
>> Zhanjun Dong
>>>
>>> This could be one call to strcat, but it is not a blocker.
>>>
>>> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>>>
>>>> + }
>>>> +
>>>> + igt_emit_ignore_dmesg_regex(regex);
>>>> +}
>>>> +
>>>> /*
>>>> * The injectable file requires CONFIG_FUNCTION_ERROR_INJECTION in kernel.
>>>> */
>>>> @@ -175,6 +199,7 @@ igt_main
>>>> if (regexec(®ex, line, 2, pmatch, 0) == 0) {
>>>> strcpy(function_name, line);
>>>> function_name[pmatch[1].rm_eo - 1] = '\0';
>>>> + ignore_faults_in_dmesg(function_name);
>>>> igt_dynamic_f("function-%s", function_name)
>>>> inject_fault_try_bind(fd, pci_slot, function_name);
>>>> }
>>>> --
>>>> 2.43.0
>>>>
>>
next prev parent reply other threads:[~2024-11-19 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 19:59 [PATCH v2] tests/intel/xe_fault_injection: Ignore expected errors Jonathan Cavitt
2024-11-07 20:13 ` ✗ GitLab.Pipeline: warning for tests/intel/xe_fault_injection: Ignore expected errors (rev2) Patchwork
2024-11-07 20:43 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-07 20:58 ` ✗ CI.xeBAT: failure " Patchwork
2024-11-07 22:22 ` ✗ Fi.CI.IGT: " Patchwork
2024-11-08 15:58 ` [PATCH v2] tests/intel/xe_fault_injection: Ignore expected errors Kamil Konieczny
2024-11-12 17:58 ` Dong, Zhanjun
2024-11-15 14:02 ` Kamil Konieczny
2024-11-19 14:31 ` Dong, Zhanjun [this message]
2024-11-09 2:54 ` ✗ CI.xeFULL: failure for tests/intel/xe_fault_injection: Ignore expected errors (rev2) Patchwork
2024-11-19 20:50 ` [PATCH v2] tests/intel/xe_fault_injection: Ignore expected errors 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=b712815e-a709-4506-9a6c-9c267ad5367c@intel.com \
--to=zhanjun.dong@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=kamil.konieczny@linux.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