Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: "K V P, Satyanarayana" <satyanarayana.k.v.p@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>,
	"Dugast, Francois" <francois.dugast@intel.com>
Subject: Re: [i-g-t,v4,2/3] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv.
Date: Fri, 4 Apr 2025 08:25:12 +0200	[thread overview]
Message-ID: <100211b9-9600-4a35-b1c4-3198cdc5e72e@intel.com> (raw)
In-Reply-To: <LV3PR11MB86951576818F866D55D961D7F9A92@LV3PR11MB8695.namprd11.prod.outlook.com>


On 4/4/2025 08:04, K V P, Satyanarayana wrote:
>> From: Laguna, Lukasz <lukasz.laguna@intel.com>
>> Sent: Thursday, April 3, 2025 7:05 PM
>> To: K V P, Satyanarayana <satyanarayana.k.v.p@intel.com>; igt-
>> dev@lists.freedesktop.org
>> Cc: De Marchi, Lucas <lucas.demarchi@intel.com>; Wajdeczko, Michal
>> <Michal.Wajdeczko@intel.com>; Dugast, Francois
>> <francois.dugast@intel.com>
>> Subject: Re: [i-g-t,v4,2/3] tests/intel/xe_fault_injection: Inject errors during
>> xe_guc_ct_send_recv & xe_guc_mmio_send_recv.
>>
>>
>> On 3/28/2025 12:15, Satyanarayana K V P wrote:
>>> Use the kernel fault injection infrastructure to test error handling
>>> of xe during driver probe when executing xe_guc_ct_send_recv() /
>>> xe_guc_mmio_send_recv() so that more code paths are tested, such as
>>> error handling and unwinding.
>>>
>>> All xe_init() kind of functions are called just once during driver probe,
>>> so it is sufficient to fail first/all calls to them. Driver communicates
>>> with the GuC multiple times, and the real failure can happen at different
>>> call, hence the need to inject failure in GuC communication functions,
>>> like guc_mmio_send() or guc_ct_send(), but it can't be just first call or
>>> all calls, but we need to be able to select specific iteration to fail.
>>>
>>> To address this problem, the environmental variable
>> IGT_FAULT_INJECT_ITERATION
>>
>> I think it'd be better to use test parameter instead of environment
>> variable. Please check igt_main_args() and consider using it.
>>
> Hi Lukasz,
>   The intention of test is to inject error 0-100 iterations for guc_ct and guc_mmio functions.
> The environment variable is used to inject error at specific iteration in case we want to debug
> Issue in case of any failure. So, not used test parameter.

I got it, but still don't see why to use environment variable instead of 
test param.

- Lukasz

>
> -Satya.
>
>   
>>> is used. If the IGT_FAULT_INJECT_ITERATION is not exported, an error will
>>> be injected in every possible function call starting from first up to the
>>> max number of iteration defined by INJECT_ITERATIONS, currently
>> hardcoded
>>> as 100. Also, using IGT_FAULT_INJECT_ITERATION, an error can be injected
>> at
>>> specific function call.
>>>
>>> Error can be injected using:
>>> igt@xe_fault_injection@probe-fail-guc-xe_guc_ct_send_recv
>>> igt@xe_fault_injection@probe-fail-guc-xe_guc_mmio_send_recv
>>>
>>> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
>>> Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
>>> Cc: Francois Dugast <francois.dugast@intel.com>
>>> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>>> ---
>>>    tests/intel/xe_fault_injection.c | 61
>> ++++++++++++++++++++++++++++++++
>>>    1 file changed, 61 insertions(+)
>>>
>>> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
>>> index 1325a1716..a49070b4d 100644
>>> --- a/tests/intel/xe_fault_injection.c
>>> +++ b/tests/intel/xe_fault_injection.c
>>> @@ -26,6 +26,7 @@
>>>    #define INJECT_ERRNO	-ENOMEM
>>>    #define BO_ADDR		0x1a0000
>>>    #define BO_SIZE		(1024*1024)
>>> +#define INJECT_ITERATIONS	100
>>>
>>>    enum injection_list_action {
>>>    	INJECTION_LIST_ADD,
>>> @@ -43,6 +44,24 @@ struct fault_injection_params {
>>>    	uint32_t space;
>>>    };
>>>
>>> +/**
>>> + *  Introduce a new environmental variable IGT_FAULT_INJECT_ITERATION
>>> + *  using which an error can be injected at specific function call.
>>> + *  When unset test will run for INJECT_ITERATIONS iterations.
>>> + *  When set to <=0 or malformed - same as unset.
>>> + *  When set to >0 it will run single n-th iteration only.
>>> + */
>>> +static int get_fault_inject_iter(void)
>>> +{
>>> +	const char *env = getenv("IGT_FAULT_INJECT_ITERATION");
>>> +
>>> +	/* Return 0 if not exported / -ve value */
>>> +	if (!env || atoi(env) <= 0)
>>> +		return 0;
>>> +
>>> +	return atoi(env);
>>> +}
>>> +
>>>    static int fail_function_open(void)
>>>    {
>>>    	int debugfs_fail_function_dir_fd;
>>> @@ -228,6 +247,34 @@ inject_fault_probe(int fd, char pci_slot[], const
>> char function_name[])
>>>    	injection_list_do(INJECTION_LIST_REMOVE, function_name);
>>>    }
>>>
>>> +/**
>>> + * SUBTEST: probe-fail-guc-%s
>>> + * Description: inject an error in the injectable function %arg[1] then
>> reprobe driver
>>> + * Functionality: fault
>>> + *
>>> + * arg[1]:
>>> + * @xe_guc_mmio_send_recv:     Inject an error when calling
>> xe_guc_mmio_send_recv
>>> + * @xe_guc_ct_send_recv:       Inject an error when calling
>> xe_guc_ct_send_recv
>>> + */
>>> +static void probe_fail_guc(int fd, char pci_slot[], const char
>> function_name[],
>>> +               struct fault_injection_params *fault_params)
>>> +{
>>> +	int iter_start = 0, iter_end = 0, iter = 0;
>>> +
>>> +	igt_assert(fault_params);
>>> +
>>> +	/* Get the iteration count from environment */
>>> +	iter = get_fault_inject_iter();
>>> +	iter_start = iter ? : 0;
>> Can't it be just iter_start = iter; ?
>>
>>> +	iter_end = iter ? iter + 1 : INJECT_ITERATIONS;
>>> +	for (int i = iter_start; i < iter_end; i++) {
>>> +		fault_params->space = i;
>>> +		setup_injection_fault(fault_params);
>>> +		inject_fault_probe(fd, pci_slot, function_name);
>>> +		igt_kmod_unbind("xe", pci_slot);
>>> +	}
>>> +}
>>> +
>>>    /**
>>>     * SUBTEST: exec-queue-create-fail-%s
>>>     * Description: inject an error in function %arg[1] used in exec queue create
>> IOCTL to make it fail
>>> @@ -406,6 +453,7 @@ igt_main
>>>    {
>>>    	int fd, sysfs;
>>>    	struct drm_xe_engine_class_instance *hwe;
>>> +	struct fault_injection_params fault_params;
>>>    	static uint32_t devid;
>>>    	char pci_slot[NAME_MAX];
>>>    	const struct section {
>>> @@ -463,6 +511,12 @@ igt_main
>>>    		{ }
>>>    	};
>>>
>>> +	const struct section guc_fail_functions[] = {
>>> +		{ "xe_guc_mmio_send_recv" },
>>> +		{ "xe_guc_ct_send_recv" },
>>> +		{ }
>>> +	};
>>> +
>>>    	igt_fixture {
>>>    		igt_require(fail_function_injection_enabled());
>>>    		fd = drm_open_driver(DRIVER_XE);
>>> @@ -505,6 +559,13 @@ igt_main
>>>    		igt_subtest_f("inject-fault-probe-function-%s", s->name)
>>>    			inject_fault_probe(fd, pci_slot, s->name);
>>>
>>> +   for (const struct section *s = guc_fail_functions; s->name; s++)
>>> +       igt_subtest_f("probe-fail-guc-%s", s->name) {
>>> +           memcpy(&fault_params, &default_fault_params,
>>> +                   sizeof(struct fault_injection_params));
>>> +           probe_fail_guc(fd, pci_slot, s->name, &fault_params);
>>> +       }
>>> +
>>>    	igt_fixture {
>>>    		close(sysfs);
>>>    		drm_close_driver(fd);

  reply	other threads:[~2025-04-04  6:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 11:15 [PATCH i-g-t v4 0/3] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv() xe_guc_mmio_send_recv() Satyanarayana K V P
2025-03-28 11:15 ` [PATCH i-g-t v4 1/3] tests/intel/xe_fault_injection: Make setup_injection_fault() programmable Satyanarayana K V P
2025-03-28 11:15 ` [PATCH i-g-t v4 2/3] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv Satyanarayana K V P
2025-04-03 13:34   ` [i-g-t,v4,2/3] " Laguna, Lukasz
2025-04-04  6:04     ` K V P, Satyanarayana
2025-04-04  6:25       ` Laguna, Lukasz [this message]
2025-04-04 15:17         ` Lucas De Marchi
2025-04-04 13:37   ` [PATCH i-g-t v4 2/3] " Kamil Konieczny
2025-03-28 11:15 ` [PATCH i-g-t v4 3/3] tests/intel/xe_fault_injection: Do not assert for probe_guc_fail_* functions Satyanarayana K V P
2025-04-03  8:13   ` Francois Dugast
2025-03-28 23:39 ` ✓ Xe.CI.BAT: success for tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv() xe_guc_mmio_send_recv() (rev4) Patchwork
2025-03-28 23:54 ` ✓ i915.CI.BAT: " Patchwork
2025-03-29  4:42 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-29 15:55 ` ✗ Xe.CI.Full: " Patchwork
2025-04-06 19:16 ` 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=100211b9-9600-4a35-b1c4-3198cdc5e72e@intel.com \
    --to=lukasz.laguna@intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@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