From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
igt-dev@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
Francois Dugast <francois.dugast@intel.com>
Subject: Re: [PATCH i-g-t v4 1/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_mmio_send_recv
Date: Wed, 22 Jan 2025 15:54:49 +0100 [thread overview]
Message-ID: <d40d4dd7-ab68-4bfc-8a12-6ff5ddf7dea0@intel.com> (raw)
In-Reply-To: <20250122073808.16288-2-satyanarayana.k.v.p@intel.com>
Hi,
some late comments below:
On 22.01.2025 08:38, 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:
> igt@xe_fault_injection@inject-fault-probe-function-xe_guc_mmio_send_recv
>
> v2: Sorted the entry xe_guc_mmio_send_recv in inject-fault-probe-function-* list
>
> 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>
> Reviewed-by: Francois Dugast <francois.dugast@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..3a0e2aa29 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -163,6 +163,7 @@ static void set_retval(const char function_name[], long long retval)
> * @xe_guc_ads_init: xe_guc_ads_init
> * @xe_guc_ct_init: xe_guc_ct_init
> * @xe_guc_log_init: xe_guc_log_init
> + * @xe_guc_mmio_send_recv: xe_guc_mmio_send_recv
hmm, I know that you are trying to follow existing comment style, but
what is the actual purpose of typing a function name twice here?
and why this sub-test documentation is so separate from the actual place
where this function is used (in igt_main far below) ?
> * @xe_guc_relay_init: xe_guc_relay_init
> * @xe_pm_init_early: xe_pm_init_early
> * @xe_sriov_init: xe_sriov_init
> @@ -294,6 +295,7 @@ igt_main
> { "xe_guc_ads_init" },
> { "xe_guc_ct_init" },
> { "xe_guc_log_init" },
> + { "xe_guc_mmio_send_recv" },
> { "xe_guc_relay_init" },
> { "xe_pm_init_early" },
> { "xe_sriov_init" },
next prev parent reply other threads:[~2025-01-22 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 7:38 [PATCH i-g-t v4 0/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv Satyanarayana K V P
2025-01-22 7:38 ` [PATCH i-g-t v4 1/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_mmio_send_recv Satyanarayana K V P
2025-01-22 14:54 ` Michal Wajdeczko [this message]
2025-01-22 7:38 ` [PATCH i-g-t v4 2/2] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv Satyanarayana K V P
2025-01-22 15:22 ` Michal Wajdeczko
2025-01-22 10:44 ` ✓ i915.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-01-22 11:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-22 21:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-23 15:00 ` ✗ i915.CI.Full: " 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=d40d4dd7-ab68-4bfc-8a12-6ff5ddf7dea0@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.brost@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