Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Aditya Chauhan <aditya.chauhan@intel.com>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v2] drm/xe: Add helper function to inject fault into ct_dead_capture()
Date: Tue, 6 May 2025 16:19:37 -0700	[thread overview]
Message-ID: <ac18b7a1-c149-4182-bc6d-6b73b943525d@intel.com> (raw)
In-Reply-To: <20250430131710.20532-1-satyanarayana.k.v.p@intel.com>

On 4/30/2025 6:17 AM, Satyanarayana K V P wrote:
> When injecting fault to xe_guc_ct_send_recv() & xe_guc_mmio_send_recv()
> functions, the CI test systems are going out of space and crashing. To
> avoid this issue, a new helper function is created and when fault is
> injected into this xe_should_fail_ct_dead_capture() helper function,
> ct dead capture is avoided which suppresses ct dumps in the log.
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Suggested-by: John Harrison <John.C.Harrison@Intel.com>
> Tested-by: Aditya Chauhan <aditya.chauhan@intel.com>
>
> ---
> Cc: Jani Nikula <jani.nikula@intel.com>
>
> V1 -> V2:
> - Fixed review comments.
> ---
>   drivers/gpu/drm/xe/xe_guc_ct.c | 21 +++++++++++++++++++++
>   1 file changed, 21 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index 2447de0ebedf..d6e7a8b80d8c 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1770,6 +1770,20 @@ void xe_guc_ct_print(struct xe_guc_ct *ct, struct drm_printer *p, bool want_ctb)
>   }
>   
>   #if IS_ENABLED(CONFIG_DRM_XE_DEBUG)
> +/**
> + * xe_should_fail_ct_dead_capture - Helper function to inject fault.
> + *
> + * This is a helper function to inject fault into ct_dead_capture().
> + * As fault is injected using this function, need to make sure that
> + * the compiler does not optimize and make it as a inline function.
> + * To prevent compile optimization, "noinline" is added.
> + */
> +static noinline int xe_should_fail_ct_dead_capture(void)
> +{
> +	return 0;
> +}
> +ALLOW_ERROR_INJECTION(xe_should_fail_ct_dead_capture, ERRNO);
> +
>   static void ct_dead_capture(struct xe_guc_ct *ct, struct guc_ctb *ctb, u32 reason_code)
>   {
>   	struct xe_guc_log_snapshot *snapshot_log;
> @@ -1778,6 +1792,13 @@ static void ct_dead_capture(struct xe_guc_ct *ct, struct guc_ctb *ctb, u32 reaso
>   	unsigned long flags;
>   	bool have_capture;
>   
> +	/*
> +	 * Huge dump is getting generated when injecting error for guc CT/MMIO
> +	 * functions. So, let us suppress the dump when fault is injected.
> +	 */
> +	if (xe_should_fail_ct_dead_capture())
Is it worth making this a more generic 'is_error_fault_injected()'? Then 
it can be used by random other bits of code if/when necessary. And maybe 
also have an inline/#define version for when 
CONFIG_FUNCTION_ERROR_INJECTION is not defined?

John.

> +		return;
> +
>   	if (ctb)
>   		ctb->info.broken = true;
>   


  parent reply	other threads:[~2025-05-06 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 13:17 [PATCH v2] drm/xe: Add helper function to inject fault into ct_dead_capture() Satyanarayana K V P
2025-04-30 15:21 ` ✓ CI.Patch_applied: success for drm/xe: Add helper function to inject fault into ct_dead_capture() (rev2) Patchwork
2025-04-30 15:21 ` ✓ CI.checkpatch: " Patchwork
2025-04-30 15:22 ` ✓ CI.KUnit: " Patchwork
2025-04-30 15:33 ` ✓ CI.Build: " Patchwork
2025-04-30 15:37 ` ✓ CI.Hooks: " Patchwork
2025-04-30 15:38 ` ✓ CI.checksparse: " Patchwork
2025-04-30 23:10 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-06  7:55 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-06 23:19 ` John Harrison [this message]
2025-05-07  5:13   ` [PATCH v2] drm/xe: Add helper function to inject fault into ct_dead_capture() K V P, Satyanarayana
2025-05-08 23:00     ` John Harrison

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=ac18b7a1-c149-4182-bc6d-6b73b943525d@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=aditya.chauhan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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