From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Alan Previn Teres Alexis <alan.previn.teres.alexis@intel.com>,
"Julia Filipchuk" <julia.filipchuk@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 3/3] drm/xe/pxp: Do a PXP termination before suspend entry
Date: Wed, 25 Feb 2026 14:42:25 -0800 [thread overview]
Message-ID: <9876f542-0c59-436b-b2b4-ce6be9aa9563@intel.com> (raw)
In-Reply-To: <20260219002627.1208210-8-daniele.ceraolospurio@intel.com>
On 2/18/2026 4:26 PM, Daniele Ceraolo Spurio wrote:
> There is a bug in the PTL GSC FW that causes the FW to sometimes crash
> after we resume from system suspend if a PXP session was still active
> when we suspended. This is being debugged from the GSC side, but in the
> meantime we can mitigate the issue by simply making sure that all PXP
> sessions are terminated before we enter system suspend. Given that there
> are no negative consequences with doing this extra termination (because
> we do a termination after we resume anyway, so the state is cleaned no
> matter what), the change is applied unconditionally for all platforms to
> keep the behavior the same.
>
> Note that the issue has not been seen so far with runtime suspend, so
> the behavior has not been modified for that case.
>
> Fixes: b1dcec9bd8a1 ("drm/xe/ptl: Enable PXP for PTL")
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7075
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Alan Previn Teres Alexis <alan.previn.teres.alexis@intel.com>
> Cc: Julia Filipchuk <julia.filipchuk@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pm.c | 4 +-
> drivers/gpu/drm/xe/xe_pxp.c | 84 +++++++++++++++++++++++--------------
> drivers/gpu/drm/xe/xe_pxp.h | 2 +-
> 3 files changed, 56 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 01185f10a883..7094b133f449 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -178,7 +178,7 @@ int xe_pm_suspend(struct xe_device *xe)
> xe_pm_block_begin_signalling();
> trace_xe_pm_suspend(xe, __builtin_return_address(0));
>
> - err = xe_pxp_pm_suspend(xe->pxp);
> + err = xe_pxp_pm_suspend(xe->pxp, true);
> if (err)
> goto err;
>
> @@ -584,7 +584,7 @@ int xe_pm_runtime_suspend(struct xe_device *xe)
> */
> xe_rpm_lockmap_acquire(xe);
>
> - err = xe_pxp_pm_suspend(xe->pxp);
> + err = xe_pxp_pm_suspend(xe->pxp, false);
> if (err)
> goto out;
>
> diff --git a/drivers/gpu/drm/xe/xe_pxp.c b/drivers/gpu/drm/xe/xe_pxp.c
> index fa82d606953e..bff20f0e5cf4 100644
> --- a/drivers/gpu/drm/xe/xe_pxp.c
> +++ b/drivers/gpu/drm/xe/xe_pxp.c
> @@ -509,6 +509,24 @@ static int __exec_queue_add(struct xe_pxp *pxp, struct xe_exec_queue *q)
> return ret;
> }
>
> +static int pxp_wait_for_events(struct xe_pxp *pxp)
> +{
> + /*
> + * if there is an action in progress, wait for it. We need to wait
> + * outside the lock because the completion is done from within the lock.
> + * Note that the two actions should never be pending at the same time.
> + */
> + if (!wait_for_completion_timeout(&pxp->termination,
> + msecs_to_jiffies(PXP_TERMINATION_TIMEOUT_MS)))
> + return -ETIMEDOUT;
> +
> + if (!wait_for_completion_timeout(&pxp->activation,
> + msecs_to_jiffies(PXP_ACTIVATION_TIMEOUT_MS)))
> + return -ETIMEDOUT;
> +
> + return 0;
> +}
> +
> static int pxp_start(struct xe_pxp *pxp, u8 type)
> {
> int ret = 0;
> @@ -528,18 +546,9 @@ static int pxp_start(struct xe_pxp *pxp, u8 type)
> ret = 0;
>
> wait_for_idle:
> - /*
> - * if there is an action in progress, wait for it. We need to wait
> - * outside the lock because the completion is done from within the lock.
> - * Note that the two actions should never be pending at the same time.
> - */
> - if (!wait_for_completion_timeout(&pxp->termination,
> - msecs_to_jiffies(PXP_TERMINATION_TIMEOUT_MS)))
> - return -ETIMEDOUT;
> -
> - if (!wait_for_completion_timeout(&pxp->activation,
> - msecs_to_jiffies(PXP_ACTIVATION_TIMEOUT_MS)))
> - return -ETIMEDOUT;
> + ret = pxp_wait_for_events(pxp);
> + if (ret)
> + return ret;
>
> mutex_lock(&pxp->mutex);
>
> @@ -827,13 +836,14 @@ int xe_pxp_obj_key_check(struct drm_gem_object *obj)
> /**
> * xe_pxp_pm_suspend - prepare PXP for HW suspend
> * @pxp: the xe->pxp pointer (it will be NULL if PXP is disabled)
> + * @terminate: terminate PXP if active before suspending
> *
> * Makes sure all PXP actions have completed and invalidates all PXP queues
> * and objects before we go into a suspend state.
> *
> * Returns: 0 if successful, a negative errno value otherwise.
> */
> -int xe_pxp_pm_suspend(struct xe_pxp *pxp)
> +int xe_pxp_pm_suspend(struct xe_pxp *pxp, bool terminate)
> {
> bool needs_queue_inval = false;
> int ret = 0;
> @@ -841,10 +851,10 @@ int xe_pxp_pm_suspend(struct xe_pxp *pxp)
> if (!xe_pxp_is_enabled(pxp))
> return 0;
>
> -wait_for_activation:
> - if (!wait_for_completion_timeout(&pxp->activation,
> - msecs_to_jiffies(PXP_ACTIVATION_TIMEOUT_MS)))
> - ret = -ETIMEDOUT;
> +wait_for_idle:
> + ret = pxp_wait_for_events(pxp);
> + if (ret)
> + return ret;
>
> mutex_lock(&pxp->mutex);
>
> @@ -852,46 +862,58 @@ int xe_pxp_pm_suspend(struct xe_pxp *pxp)
> case XE_PXP_ERROR:
> case XE_PXP_READY_TO_START:
> case XE_PXP_SUSPENDED:
> - case XE_PXP_TERMINATION_IN_PROGRESS:
> case XE_PXP_NEEDS_ADDITIONAL_TERMINATION:
I was going through this patch which Julia and she made me notice that
the additional termination case should be treated like the termination
in progress case, because additional termination is a subcase of
termination in progress that indicates that we need a second termination
after the current one in progress is done.
Will respin with this fixed.
Daniele
> /*
> * If PXP is not running there is nothing to cleanup. If there
> * is a termination pending then no need to issue another one.
> */
> break;
> + case XE_PXP_TERMINATION_IN_PROGRESS:
> case XE_PXP_START_IN_PROGRESS:
> mutex_unlock(&pxp->mutex);
> - goto wait_for_activation;
> + goto wait_for_idle;
> case XE_PXP_NEEDS_TERMINATION:
> /* If PXP was never used we can skip the cleanup */
> if (pxp->key_instance == pxp->last_suspend_key_instance)
> break;
> fallthrough;
> case XE_PXP_ACTIVE:
> - pxp->key_instance++;
> + if (terminate)
> + mark_termination_in_progress(pxp);
> needs_queue_inval = true;
> + pxp->key_instance++;
> break;
> }
>
> /*
> - * We set this even if we were in error state, hoping the suspend clears
> - * the error. Worse case we fail again and go in error state again.
> + * If we're not taking any action (i.e. we're not triggering a
> + * termination), we set this even if we were in error state, hoping the
> + * suspend clears the error. Worst case we fail again and go in error
> + * state again.
> */
> - pxp->status = XE_PXP_SUSPENDED;
> + if (completion_done(&pxp->termination))
> + pxp->status = XE_PXP_SUSPENDED;
>
> mutex_unlock(&pxp->mutex);
>
> if (needs_queue_inval)
> pxp_invalidate_queues(pxp);
>
> - /*
> - * if there is a termination in progress, wait for it.
> - * We need to wait outside the lock because the completion is done from
> - * within the lock
> - */
> - if (!wait_for_completion_timeout(&pxp->termination,
> - msecs_to_jiffies(PXP_TERMINATION_TIMEOUT_MS)))
> - ret = -ETIMEDOUT;
> + if (!completion_done(&pxp->termination)) {
> + ret = pxp_terminate_hw(pxp);
> + if (ret) {
> + drm_err(&pxp->xe->drm, "PXP termination failed before suspend\n");
> + mutex_lock(&pxp->mutex);
> + pxp->status = XE_PXP_ERROR;
> + complete_all(&pxp->termination);
> + mutex_unlock(&pxp->mutex);
> + return ret;
> + }
> +
> + goto wait_for_idle;
> + }
> +
> + ret = kcr_pxp_disable(pxp);
>
> pxp->last_suspend_key_instance = pxp->key_instance;
>
> diff --git a/drivers/gpu/drm/xe/xe_pxp.h b/drivers/gpu/drm/xe/xe_pxp.h
> index 71a23280b900..2fe2a8bab127 100644
> --- a/drivers/gpu/drm/xe/xe_pxp.h
> +++ b/drivers/gpu/drm/xe/xe_pxp.h
> @@ -21,7 +21,7 @@ int xe_pxp_get_readiness_status(struct xe_pxp *pxp);
> int xe_pxp_init(struct xe_device *xe);
> void xe_pxp_irq_handler(struct xe_device *xe, u16 iir);
>
> -int xe_pxp_pm_suspend(struct xe_pxp *pxp);
> +int xe_pxp_pm_suspend(struct xe_pxp *pxp, bool terminate);
> void xe_pxp_pm_resume(struct xe_pxp *pxp);
>
> int xe_pxp_exec_queue_set_type(struct xe_pxp *pxp, struct xe_exec_queue *q, u8 type);
next prev parent reply other threads:[~2026-02-25 22:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 0:26 [PATCH 0/3] drm/xe: PXP fixes Daniele Ceraolo Spurio
2026-02-19 0:26 ` [PATCH 1/3] drm/xe/pxp: Clean up termination status on failure Daniele Ceraolo Spurio
2026-02-23 22:14 ` Julia Filipchuk
2026-02-23 22:29 ` Daniele Ceraolo Spurio
2026-02-23 23:51 ` Julia Filipchuk
2026-02-19 0:26 ` [PATCH 2/3] drm/xe/pxp: Remove incorrect handling of impossible state during suspend Daniele Ceraolo Spurio
2026-02-23 22:42 ` Julia Filipchuk
2026-02-23 22:48 ` Daniele Ceraolo Spurio
2026-02-23 23:54 ` Julia Filipchuk
2026-02-19 0:26 ` [PATCH 3/3] drm/xe/pxp: Do a PXP termination before suspend entry Daniele Ceraolo Spurio
2026-02-23 23:50 ` Julia Filipchuk
2026-02-25 22:42 ` Daniele Ceraolo Spurio [this message]
2026-02-19 1:22 ` ✓ CI.KUnit: success for drm/xe: PXP fixes Patchwork
2026-02-19 1:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-19 2:56 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-19 11:46 ` 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=9876f542-0c59-436b-b2b4-ce6be9aa9563@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@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