From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: <stable@vger.kernel.org>, Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v9 3/7] drm/xe: Trigger queue cleanup if not in wedged mode 2
Date: Wed, 11 Mar 2026 12:33:54 -0400 [thread overview]
Message-ID: <e9979dfc-eaab-413e-963f-a50985018e18@intel.com> (raw)
In-Reply-To: <20260310225039.1320161-4-zhanjun.dong@intel.com>
On 2026-03-10 6:50 p.m., Zhanjun Dong wrote:
> The intent of wedging a device is to allow queues to continue running
> only in wedged mode 2. In other modes, queues should initiate cleanup
> and signal all remaining fences. Fix xe_guc_submit_wedge to correctly
> clean up queues when wedge mode != 2.
>
> Fixes: 7dbe8af13c18 ("drm/xe: Wedge the entire device")
> Cc: stable@vger.kernel.org
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 35 +++++++++++++++++++-----------
> 1 file changed, 22 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 8afd424b27fb..cb32053d57ec 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1319,6 +1319,7 @@ static void disable_scheduling_deregister(struct xe_guc *guc,
> */
> void xe_guc_submit_wedge(struct xe_guc *guc)
> {
> + struct xe_device *xe = guc_to_xe(guc);
> struct xe_gt *gt = guc_to_gt(guc);
> struct xe_exec_queue *q;
> unsigned long index;
> @@ -1333,20 +1334,28 @@ void xe_guc_submit_wedge(struct xe_guc *guc)
> if (!guc->submission_state.initialized)
> return;
>
> - err = devm_add_action_or_reset(guc_to_xe(guc)->drm.dev,
> - guc_submit_wedged_fini, guc);
> - if (err) {
> - xe_gt_err(gt, "Failed to register clean-up in wedged.mode=%s; "
> - "Although device is wedged.\n",
> - xe_wedged_mode_to_string(XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET));
> - return;
> - }
> + if (xe->wedged.mode == 2) {
> + err = devm_add_action_or_reset(guc_to_xe(guc)->drm.dev,
> + guc_submit_wedged_fini, guc);
> + if (err) {
> + xe_gt_err(gt, "Failed to register clean-up on wedged.mode=2; "
> + "Although device is wedged.\n");
> + return;
> + }
>
> - mutex_lock(&guc->submission_state.lock);
> - xa_for_each(&guc->submission_state.exec_queue_lookup, index, q)
> - if (xe_exec_queue_get_unless_zero(q))
> - set_exec_queue_wedged(q);
> - mutex_unlock(&guc->submission_state.lock);
> + mutex_lock(&guc->submission_state.lock);
> + xa_for_each(&guc->submission_state.exec_queue_lookup, index, q)
> + if (xe_exec_queue_get_unless_zero(q))
> + set_exec_queue_wedged(q);
> + mutex_unlock(&guc->submission_state.lock);
> + } else {
> + /* Forcefully kill any remaining exec queues, signal fences */
Q: Shall we do VF bypass here?
Regards,
Zhanjun Dong
> + guc_submit_reset_prepare(guc);
> + xe_guc_submit_stop(guc);
> + xe_guc_softreset(guc);
> + xe_uc_fw_sanitize(&guc->fw);
> + xe_guc_submit_pause_abort(guc);
> + }
> }
>
> static bool guc_submit_hint_wedged(struct xe_guc *guc)
next prev parent reply other threads:[~2026-03-11 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260310225039.1320161-1-zhanjun.dong@intel.com>
2026-03-10 22:50 ` [PATCH v9 1/7] drm/xe: Always kill exec queues in xe_guc_submit_pause_abort Zhanjun Dong
2026-03-10 22:50 ` [PATCH v9 2/7] drm/xe: Forcefully tear down exec queues in GuC submit fini Zhanjun Dong
2026-03-11 16:34 ` Dong, Zhanjun
2026-03-13 18:48 ` Matthew Brost
2026-03-13 20:30 ` Dong, Zhanjun
2026-03-10 22:50 ` [PATCH v9 3/7] drm/xe: Trigger queue cleanup if not in wedged mode 2 Zhanjun Dong
2026-03-11 16:33 ` Dong, Zhanjun [this message]
2026-03-13 18:49 ` Matthew Brost
2026-03-13 20:31 ` Dong, Zhanjun
2026-03-10 22:50 ` [PATCH v9 5/7] drm/xe/guc: Ensure CT state transitions via STOP before DISABLED Zhanjun Dong
2026-03-10 22:50 ` [PATCH v9 7/7] drm/xe: Open-code GGTT MMIO access protection Zhanjun Dong
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=e9979dfc-eaab-413e-963f-a50985018e18@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox