All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>,
	stable@vger.kernel.org, Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH v8 5/7] drm/xe/guc: Ensure CT state transitions via STOP before DISABLED
Date: Tue, 24 Feb 2026 11:35:53 -0500	[thread overview]
Message-ID: <20260224163555.218750-6-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20260224163555.218750-1-zhanjun.dong@intel.com>

The GuC CT state transition requires moving to the STOP state before
entering the DISABLED state. Update the driver teardown sequence to make
the proper state machine transitions.

Fixes: ee4b32220a6b ("drm/xe/guc: Add devm release action to safely tear down CT")
Cc: stable@vger.kernel.org
Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_guc_ct.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
index 8a45573f8812..7e66e9420f5d 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -346,6 +346,7 @@ static void guc_action_disable_ct(void *arg)
 {
 	struct xe_guc_ct *ct = arg;
 
+	xe_guc_ct_stop(ct);
 	guc_ct_change_state(ct, XE_GUC_CT_STATE_DISABLED);
 }
 
-- 
2.34.1


  parent reply	other threads:[~2026-02-24 16:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 16:35 [PATCH v8 0/7] Attempt to fixup reset, wedge, unload corner cases Zhanjun Dong
2026-02-24 16:35 ` [PATCH v8 1/7] drm/xe: Always kill exec queues in xe_guc_submit_pause_abort Zhanjun Dong
2026-02-24 16:35 ` [PATCH v8 2/7] drm/xe: Forcefully tear down exec queues in GuC submit fini Zhanjun Dong
2026-02-24 16:35 ` [PATCH v8 3/7] drm/xe: Trigger queue cleanup if not in wedged mode 2 Zhanjun Dong
2026-02-24 16:35 ` [PATCH v8 4/7] drm/xe: Use XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET enum instead of magic number Zhanjun Dong
2026-02-24 16:35 ` Zhanjun Dong [this message]
2026-02-24 16:35 ` [PATCH v8 6/7] drm/xe/uc: Drop xe_guc_sanitize in favor of managed cleanup Zhanjun Dong
2026-02-24 16:35 ` [PATCH v8 7/7] drm/xe: Open-code GGTT MMIO access protection Zhanjun Dong
2026-03-05 15:22   ` Dong, Zhanjun
2026-02-24 16:43 ` ✓ CI.KUnit: success for Attempt to fixup reset, wedge, unload corner cases Patchwork
2026-02-26  0:43 ` ✓ CI.KUnit: success for Attempt to fixup reset, wedge, unload corner cases (rev2) Patchwork
2026-02-26  1:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-26  4:45 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-06 21:13 ` ✓ CI.KUnit: success for Attempt to fixup reset, wedge, unload corner cases (rev3) Patchwork
2026-03-06 21:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-08  0:26 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-09 21:52   ` Dong, Zhanjun

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=20260224163555.218750-6-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=stable@vger.kernel.org \
    /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.