All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
	John Harrison <John.C.Harrison@Intel.com>,
	Aditya Chauhan <aditya.chauhan@intel.com>
Subject: Re: [PATCH] drm/xe: Add helper function to inject fault into ct_dead_capture()
Date: Wed, 30 Apr 2025 15:01:58 +0300	[thread overview]
Message-ID: <87h625vow9.fsf@intel.com> (raw)
In-Reply-To: <20250429134649.4747-1-satyanarayana.k.v.p@intel.com>

On Tue, 29 Apr 2025, Satyanarayana K V P <satyanarayana.k.v.p@intel.com> 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>
> ---
>  drivers/gpu/drm/xe/xe_guc_ct.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index 2447de0ebedf..3a49e432f74a 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1770,6 +1770,12 @@ void xe_guc_ct_print(struct xe_guc_ct *ct, struct drm_printer *p, bool want_ctb)
>  }
>  
>  #if IS_ENABLED(CONFIG_DRM_XE_DEBUG)
> +static noinline int xe_should_fail_ct_dead_capture(void)

IMO noinline needs an explanation. I can guess, but let's not make
everyone guess.

BR,
Jani.

> +{
> +	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 +1784,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())
> +		return;
> +
>  	if (ctb)
>  		ctb->info.broken = true;

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-04-30 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 13:46 [PATCH] drm/xe: Add helper function to inject fault into ct_dead_capture() Satyanarayana K V P
2025-04-29 13:35 ` ✓ CI.Patch_applied: success for " Patchwork
2025-04-29 13:36 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-29 13:37 ` ✓ CI.KUnit: success " Patchwork
2025-04-29 13:45 ` ✓ CI.Build: " Patchwork
2025-04-29 13:47 ` ✓ CI.Hooks: " Patchwork
2025-04-29 13:49 ` ✓ CI.checksparse: " Patchwork
2025-04-29 16:35 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-30 12:01 ` Jani Nikula [this message]
2025-04-30 13:01   ` [PATCH] " K V P, Satyanarayana
2025-05-06  7:52 ` ✓ Xe.CI.BAT: success for " 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=87h625vow9.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=aditya.chauhan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.