From: Francois Dugast <francois.dugast@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: igt-dev@lists.freedesktop.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Michał Wajdeczko" <michal.wajdeczko@intel.com>
Subject: Re: [PATCH 1/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_mmio_send_recv
Date: Fri, 17 Jan 2025 13:49:24 +0100 [thread overview]
Message-ID: <Z4pR1PnwDkRSlb1O@fdugast-desk> (raw)
In-Reply-To: <20241230084451.17488-2-satyanarayana.k.v.p@intel.com>
Hi,
On Mon, Dec 30, 2024 at 02:14:50PM +0530, Satyanarayana K V P wrote:
> Use the kernel fault injection infrastructure to test error handling
> of xe at probe time when executing xe_guc_mmio_send_recv() so that
> more code paths are tested, such as error handling and unwinding.
>
> Error can be injected using:
> ./xe_fault_injection --run-subtest inject-fault-probe-function-xe_guc_mmio_send_recv
>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> ---
> tests/intel/xe_fault_injection.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
> index 7ae941367..ef3bbb7ec 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -170,6 +170,7 @@ static void set_retval(const char function_name[], long long retval)
> * @xe_uc_fw_init: xe_uc_fw_init
> * @xe_wa_init: xe_wa_init
> * @xe_wopcm_init: xe_wopcm_init
> + * @xe_guc_mmio_send_recv: xe_guc_mmio_send_recv
Please keep this list sorted.
> */
> static void
> inject_fault_probe(int fd, char pci_slot[], const char function_name[])
> @@ -301,6 +302,7 @@ igt_main
> { "xe_uc_fw_init" },
> { "xe_wa_init" },
> { "xe_wopcm_init" },
> + { "xe_guc_mmio_send_recv" },
Please also keep this list sorted.
Francois
> { }
> };
> const struct section vm_create_fail_functions[] = {
> --
> 2.35.3
>
next prev parent reply other threads:[~2025-01-17 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 8:44 [PATCH 0/2] Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv Satyanarayana K V P
2024-12-30 8:44 ` [PATCH 1/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_mmio_send_recv Satyanarayana K V P
2025-01-17 12:49 ` Francois Dugast [this message]
2024-12-30 8:44 ` [PATCH 2/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv Satyanarayana K V P
2025-01-17 13:19 ` Francois Dugast
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=Z4pR1PnwDkRSlb1O@fdugast-desk \
--to=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@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