From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/pm: Add lockdep annotation for the pm_block completion
Date: Fri, 19 Sep 2025 13:04:01 +0200 [thread overview]
Message-ID: <b806599df64b052f54d8da37f03bb66c1375dea6.camel@linux.intel.com> (raw)
In-Reply-To: <55ad501d-f73c-4ce1-87d6-8f5d0bd59d41@intel.com>
On Fri, 2025-09-19 at 12:00 +0100, Matthew Auld wrote:
> On 18/09/2025 15:28, Thomas Hellström wrote:
> > Similar to how we annotate dma-fences, add lockep annotation to
> > the pm_block completion to ensure we don't wait for it while
> > holding
> > locks that are needed in the pm notifier or in the device
> > suspend / resume callbacks.
> >
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_exec.c | 3 +-
> > drivers/gpu/drm/xe/xe_pm.c | 59
> > ++++++++++++++++++++++++++++++++++++
> > drivers/gpu/drm/xe/xe_pm.h | 2 ++
> > drivers/gpu/drm/xe/xe_vm.c | 2 ++
> > 4 files changed, 65 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_exec.c
> > b/drivers/gpu/drm/xe/xe_exec.c
> > index 7715e74bb945..83897950f0da 100644
> > --- a/drivers/gpu/drm/xe/xe_exec.c
> > +++ b/drivers/gpu/drm/xe/xe_exec.c
> > @@ -16,6 +16,7 @@
> > #include "xe_exec_queue.h"
> > #include "xe_hw_engine_group.h"
> > #include "xe_macros.h"
> > +#include "xe_pm.h"
> > #include "xe_ring_ops_types.h"
> > #include "xe_sched_job.h"
> > #include "xe_sync.h"
> > @@ -247,7 +248,7 @@ int xe_exec_ioctl(struct drm_device *dev, void
> > *data, struct drm_file *file)
> > * on task freezing during suspend / hibernate, the call
> > will
> > * return -ERESTARTSYS and the IOCTL will be rerun.
> > */
> > - err = wait_for_completion_interruptible(&xe->pm_block);
> > + err = xe_pm_block_on_suspend(xe);
> > if (err)
> > goto err_unlock_list;
> >
> > diff --git a/drivers/gpu/drm/xe/xe_pm.c
> > b/drivers/gpu/drm/xe/xe_pm.c
> > index b1c536b39034..5c561d3c3515 100644
> > --- a/drivers/gpu/drm/xe/xe_pm.c
> > +++ b/drivers/gpu/drm/xe/xe_pm.c
> > @@ -82,8 +82,58 @@ static struct lockdep_map
> > xe_pm_runtime_d3cold_map = {
> > static struct lockdep_map xe_pm_runtime_nod3cold_map = {
> > .name = "xe_rpm_nod3cold_map"
> > };
> > +
> > +static struct lockdep_map xe_pm_block_lockdep_map = {
> > + .name = "xe_pm_block_map",
> > +};
> > #endif
> >
> > +static void xe_pm_block_begin_signalling(void)
> > +{
> > + lock_acquire_shared_recursive(&xe_pm_block_lockdep_map, 0,
> > 1, NULL, _RET_IP_);
> > +}
> > +
> > +static void xe_pm_block_end_signalling(void)
> > +{
> > + lock_release(&xe_pm_block_lockdep_map, _RET_IP_);
> > +}
> > +
> > +/**
> > + * xe_pm_might_block_on_suspend() - Annotate that the code might
> > block on suspend
> > + *
> > + * Annotation to use where the code might block or sieze to make
> > + * progress pending resume completion.
> > + */
> > +void xe_pm_might_block_on_suspend(void)
> > +{
> > + lock_map_acquire(&xe_pm_block_lockdep_map);
> > + lock_map_release(&xe_pm_block_lockdep_map);
> > +}
> > +
> > +/**
> > + * xe_pm_might_block_on_suspend() - Block pending suspend.
> > + * @xe: The xe device about to be suspended.
> > + *
> > + * Block if the pm notifier has start evicting bos, to avoid
> > + * racing and validating those bos back. The function is
> > + * annotated to ensure no locks are held that are also grabbed
> > + * in the pm notifier or the device suspend / resume.
> > + * This is intended to be used by freezable tasks only.
> > + * (Not freezable workqueues), with the intention that the
> > function
> > + * returns %-ERESTARTSYS when tasks are frozen during suspend,
> > + * and allows the task to freeze. The caller must be able to
> > + * handle the %-ERESTARTSYS.
> > + *
> > + * Return: %0 on success, %-ERESTARTSYS on signal pending or
> > + * if freezing requested.
> > + */
> > +int xe_pm_block_on_suspend(struct xe_device *xe)
> > +{
> > + xe_pm_might_block_on_suspend();
> > +
> > + return wait_for_completion_interruptible(&xe->pm_block);
> > +}
> > +
> > /**
> > * xe_rpm_reclaim_safe() - Whether runtime resume can be done
> > from reclaim context
> > * @xe: The xe device.
> > @@ -123,6 +173,7 @@ int xe_pm_suspend(struct xe_device *xe)
> > int err;
> >
> > drm_dbg(&xe->drm, "Suspending device\n");
> > + xe_pm_block_begin_signalling();
> > trace_xe_pm_suspend(xe, __builtin_return_address(0));
> >
> > err = xe_pxp_pm_suspend(xe->pxp);
> > @@ -152,6 +203,8 @@ int xe_pm_suspend(struct xe_device *xe)
> > xe_i2c_pm_suspend(xe);
> >
> > drm_dbg(&xe->drm, "Device suspended\n");
> > + xe_pm_block_end_signalling();
> > +
> > return 0;
> >
> > err_display:
> > @@ -159,6 +212,7 @@ int xe_pm_suspend(struct xe_device *xe)
> > xe_pxp_pm_resume(xe->pxp);
> > err:
> > drm_dbg(&xe->drm, "Device suspend failed %d\n", err);
> > + xe_pm_block_end_signalling();
> > return err;
> > }
> >
> > @@ -175,6 +229,7 @@ int xe_pm_resume(struct xe_device *xe)
> > u8 id;
> > int err;
> >
> > + xe_pm_block_begin_signalling();
> > drm_dbg(&xe->drm, "Resuming device\n");
> > trace_xe_pm_resume(xe, __builtin_return_address(0));
> >
> > @@ -217,9 +272,11 @@ int xe_pm_resume(struct xe_device *xe)
> > xe_sriov_vf_ccs_register_context(xe);
> >
> > drm_dbg(&xe->drm, "Device resumed\n");
> > + xe_pm_block_end_signalling();
> > return 0;
> > err:
> > drm_dbg(&xe->drm, "Device resume failed %d\n", err);
> > + xe_pm_block_end_signalling();
> > return err;
> > }
> >
> > @@ -324,6 +381,7 @@ static int xe_pm_notifier_callback(struct
> > notifier_block *nb,
> > struct xe_validation_ctx ctx;
> >
> > reinit_completion(&xe->pm_block);
> > + xe_pm_block_begin_signalling();
> > xe_pm_runtime_get(xe);
> > (void)xe_validation_ctx_init(&ctx, &xe->val, NULL,
> > (struct xe_val_flags)
> > {.exclusive = true});
> > @@ -340,6 +398,7 @@ static int xe_pm_notifier_callback(struct
> > notifier_block *nb,
> > * avoid a runtime suspend interfering with
> > evicted objects or backup
> > * allocations.
> > */
> > + xe_pm_block_end_signalling();
>
> I guess ideally this would somehow be extended to the complete_all()
> below, but that would then pull in loads of unrelated stuff?
Yes, unfortunately it doesn't cover everything. But AFAICT at least
what we do in the driver.
Thanks for reviewing!
/Thomas
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> > break;
> > }
> > case PM_POST_HIBERNATION:
> > diff --git a/drivers/gpu/drm/xe/xe_pm.h
> > b/drivers/gpu/drm/xe/xe_pm.h
> > index 59678b310e55..f7f89a18b6fc 100644
> > --- a/drivers/gpu/drm/xe/xe_pm.h
> > +++ b/drivers/gpu/drm/xe/xe_pm.h
> > @@ -33,6 +33,8 @@ int xe_pm_set_vram_threshold(struct xe_device
> > *xe, u32 threshold);
> > void xe_pm_d3cold_allowed_toggle(struct xe_device *xe);
> > bool xe_rpm_reclaim_safe(const struct xe_device *xe);
> > struct task_struct *xe_pm_read_callback_task(struct xe_device
> > *xe);
> > +int xe_pm_block_on_suspend(struct xe_device *xe);
> > +void xe_pm_might_block_on_suspend(void);
> > int xe_pm_module_init(void);
> >
> > #endif
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c
> > b/drivers/gpu/drm/xe/xe_vm.c
> > index 0cacab20ff85..80b7f13ecd80 100644
> > --- a/drivers/gpu/drm/xe/xe_vm.c
> > +++ b/drivers/gpu/drm/xe/xe_vm.c
> > @@ -466,6 +466,8 @@ static void preempt_rebind_work_func(struct
> > work_struct *w)
> > retry:
> > if (!try_wait_for_completion(&vm->xe->pm_block) &&
> > vm_suspend_rebind_worker(vm)) {
> > up_write(&vm->lock);
> > + /* We don't actually block but don't make
> > progress. */
> > + xe_pm_might_block_on_suspend();
> > return;
> > }
> >
>
next prev parent reply other threads:[~2025-09-19 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 14:28 [PATCH 0/2] Suspend improvements Thomas Hellström
2025-09-18 14:28 ` [PATCH 1/2] drm/xe/pm: Hold the validation lock around evicting user-space bos for suspend Thomas Hellström
2025-09-19 10:13 ` Matthew Auld
2025-09-18 14:28 ` [PATCH 2/2] drm/xe/pm: Add lockdep annotation for the pm_block completion Thomas Hellström
2025-09-19 11:00 ` Matthew Auld
2025-09-19 11:04 ` Thomas Hellström [this message]
2025-09-18 16:03 ` ✓ CI.KUnit: success for Suspend improvements Patchwork
2025-09-18 16:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-19 1:17 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-23 12:37 ` Thomas Hellström
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=b806599df64b052f54d8da37f03bb66c1375dea6.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@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