Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"Gupta, Saurabhg" <saurabhg.gupta@intel.com>,
	"Zuo, Alex" <alex.zuo@intel.com>
Subject: Re: [PATCH] drm/xe/xe_guc_ct: Drop smp_mb in parse_g2h_response
Date: Thu, 18 Dec 2025 20:55:45 +0000	[thread overview]
Message-ID: <f25368be9cc3525a139439fb6424dc6a57b9f20a.camel@intel.com> (raw)
In-Reply-To: <20251218165803.9042-2-jonathan.cavitt@intel.com>

On Thu, 2025-12-18 at 16:58 +0000, Jonathan Cavitt wrote:
> smp_mb before wake_up_all in parse_g2h_response is superfluous.
> Drop it.
> 
> Suggested-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_guc_ct.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c
> b/drivers/gpu/drm/xe/xe_guc_ct.c
> index c3df9b3f1b4d..d101b37106da 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1499,7 +1499,6 @@ static int parse_g2h_response(struct xe_guc_ct
> *ct, u32 *msg, u32 len)
>         g2h_release_space(ct, GUC_CTB_HXG_MSG_MAX_LEN);
>  
>         g2h_fence->done = true;
> -       smp_mb();

I might be missing something here, but where is this getting called in
the current context? I see if we use woken_wake_function() this is
called there, but it looks like we would need to explicitly add that
like what is being done in the i915 driver:
DEFINE_WAIT_FUNC(wait, woken_wake_function);

Which I don't see us doing here. Should we use this wait function
instead?

Thanks,
Stuart

>  
>         wake_up_all(&ct->g2h_fence_wq);
>  


  parent reply	other threads:[~2025-12-18 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 16:58 [PATCH] drm/xe/xe_guc_ct: Drop smp_mb in parse_g2h_response Jonathan Cavitt
2025-12-18 18:52 ` ✓ CI.KUnit: success for " Patchwork
2025-12-18 19:27 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-18 20:55 ` Summers, Stuart [this message]
2025-12-19 17:47 ` ✗ Xe.CI.Full: failure " 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=f25368be9cc3525a139439fb6424dc6a57b9f20a.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=alex.zuo@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=saurabhg.gupta@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