From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com, alex.zuo@intel.com,
jonathan.cavitt@intel.com, matthew.brost@intel.com,
daniele.ceraolospurio@intel.com, rodrigo.vivi@intel.com,
michal.wajdeczko@intel.com, stuart.summers@intel.com,
dixit.ashutosh@intel.com
Subject: [PATCH v2 4/4] drm/xe/guc: READ_ONCE ct state in xe_guc_ct_initialized
Date: Thu, 18 Dec 2025 21:29:51 +0000 [thread overview]
Message-ID: <20251218212946.16577-10-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20251218212946.16577-6-jonathan.cavitt@intel.com>
Use READ_ONCE when reading ct->state in xe_guc_ct_initialized to prevent
the compiler from ignoring this operation.
Fixes: 0b93b7dcd9eb ("drm/xe: Fix early wedge on GuC load failure")
Suggested-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
---
drivers/gpu/drm/xe/xe_guc_ct.c | 5 ++++-
drivers/gpu/drm/xe/xe_guc_ct.h | 3 ++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index c59e38189cf0..24857c2c8cb5 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -530,7 +530,10 @@ static void guc_ct_change_state(struct xe_guc_ct *ct,
xe_pm_runtime_put(ct_to_xe(ct));
ct->g2h_outstanding = 0;
- /* WRITE_ONCE pairs with READ_ONCE in xe_guc_ct_enabled. */
+ /*
+ * WRITE_ONCE pairs with READ_ONCEs in xe_guc_ct_initialized and
+ * xe_guc_ct_enabled.
+ */
WRITE_ONCE(ct->state, state);
xe_gt_dbg(gt, "GuC CT communication channel %s\n",
diff --git a/drivers/gpu/drm/xe/xe_guc_ct.h b/drivers/gpu/drm/xe/xe_guc_ct.h
index 5f2811a06833..767365a33dee 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.h
+++ b/drivers/gpu/drm/xe/xe_guc_ct.h
@@ -30,7 +30,8 @@ void xe_guc_ct_print(struct xe_guc_ct *ct, struct drm_printer *p, bool want_ctb)
static inline bool xe_guc_ct_initialized(struct xe_guc_ct *ct)
{
- return ct->state != XE_GUC_CT_STATE_NOT_INITIALIZED;
+ /* READ_ONCE pairs with WRITE_ONCE in guc_ct_change_state. */
+ return READ_ONCE(ct->state) != XE_GUC_CT_STATE_NOT_INITIALIZED;
}
static inline bool xe_guc_ct_enabled(struct xe_guc_ct *ct)
--
2.43.0
next prev parent reply other threads:[~2025-12-18 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 21:29 [PATCH v2 0/4] drm/xe/guc: Prevent compiler read/write optimization breaks Jonathan Cavitt
2025-12-18 21:29 ` [PATCH v2 1/4] drm/xe/guc: WRITE_ONCE g2h_fence done in g2h_fence_cancel Jonathan Cavitt
2025-12-18 21:29 ` [PATCH v2 2/4] drm/xe/guc: WRITE_ONCE g2h_fence done in parse_g2h_response Jonathan Cavitt
2025-12-18 21:29 ` [PATCH v2 3/4] drm/xe/guc: READ/WRITE_ONCE ct state in ct_change_state and enabled Jonathan Cavitt
2025-12-18 21:29 ` Jonathan Cavitt [this message]
2025-12-18 21:31 ` [PATCH v2 0/4] drm/xe/guc: Prevent compiler read/write optimization breaks Cavitt, Jonathan
2025-12-18 22:17 ` ✓ CI.KUnit: success for " Patchwork
2025-12-18 23:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-20 0:24 ` ✗ 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=20251218212946.16577-10-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dixit.ashutosh@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=stuart.summers@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