Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
	<john.c.harrison@intel.com>, <himal.prasad.ghimiray@intel.com>,
	<rodrigo.vivi@intel.com>, <matthew.auld@intel.com>
Subject: Re: [PATCH v3 1/1] drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout
Date: Thu, 17 Oct 2024 15:17:06 +0000	[thread overview]
Message-ID: <ZxEqcndONyuZp6+l@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20241017111410.2553784-2-badal.nilawar@intel.com>

On Thu, Oct 17, 2024 at 04:44:10PM +0530, Badal Nilawar wrote:
> In case if g2h worker doesn't get opportunity to within specified
> timeout delay then flush the g2h worker explicitly.
> 
> v2:
>   - Describe change in the comment and add TODO (Matt B/John H)
>   - Add xe_gt_warn on fence done after G2H flush (John H)
> v3:
>   - Updated the comment with root cause
>   - Clean up xe_gt_warn message (John H)
> 
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1620
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2902
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>

Acked-by: Matthew Brost <matthew.brost@intel.com>

> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_guc_ct.c | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index c7673f56d413..c260d8840990 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1018,6 +1018,24 @@ static int guc_ct_send_recv(struct xe_guc_ct *ct, const u32 *action, u32 len,
>  
>  	ret = wait_event_timeout(ct->g2h_fence_wq, g2h_fence.done, HZ);
>  
> +	/*
> +	 * Occasionally it is seen that the G2H worker starts running after a delay of more than
> +	 * a second even after being queued and activated by the Linux workqueue subsystem. This
> +	 * leads to G2H timeout error. The root cause of issue lies with scheduling latency of
> +	 * Lunarlake Hybrid CPU. Issue dissappears if we disable Lunarlake atom cores from BIOS
> +	 * and this is beyond xe kmd.
> +	 *
> +	 * TODO: Drop this change once workqueue scheduling delay issue is fixed on LNL Hybrid CPU.
> +	 */
> +	if (!ret) {
> +		flush_work(&ct->g2h_worker);
> +		if (g2h_fence.done) {
> +			xe_gt_warn(gt, "G2H fence %u, action %04x, done\n",
> +				   g2h_fence.seqno, action[0]);
> +			ret = 1;
> +		}
> +	}
> +
>  	/*
>  	 * Ensure we serialize with completion side to prevent UAF with fence going out of scope on
>  	 * the stack, since we have no clue if it will fire after the timeout before we can erase
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2024-10-17 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 11:14 [PATCH v3 0/1] Workaround to handle G2H timeout Badal Nilawar
2024-10-17 11:14 ` [PATCH v3 1/1] drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout Badal Nilawar
2024-10-17 13:43   ` Ghimiray, Himal Prasad
2024-10-17 15:17   ` Matthew Brost [this message]
2024-10-18  0:05   ` John Harrison
2024-10-17 11:15 ` ✓ CI.Patch_applied: success for Workaround to handle G2H timeout (rev2) Patchwork
2024-10-17 11:15 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 11:16 ` ✓ CI.KUnit: " Patchwork
2024-10-17 11:28 ` ✓ CI.Build: " Patchwork
2024-10-17 11:30 ` ✓ CI.Hooks: " Patchwork
2024-10-17 11:32 ` ✓ CI.checksparse: " Patchwork
2024-10-17 22:36 ` ✗ CI.FULL: failure " Patchwork
2024-10-18  3:49 ` ✓ CI.BAT: success " 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=ZxEqcndONyuZp6+l@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=rodrigo.vivi@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