From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
stable@vger.kernel.org, Matthew Brost <matthew.brost@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH v2 2/3] drm/xe: Allow the pm notifier to continue on failure
Date: Tue, 2 Sep 2025 11:32:33 +0100 [thread overview]
Message-ID: <f16b5123-ed53-45b3-ac13-656ad839e87f@intel.com> (raw)
In-Reply-To: <20250901083829.27341-3-thomas.hellstrom@linux.intel.com>
On 01/09/2025 09:38, Thomas Hellström wrote:
> Its actions are opportunistic anyway and will be completed
> on device suspend.
If it fails here, it will likely also fail in the real suspend part
which is more hostile/restrictive environment, so maybe failing early is
better? Not completely sure though.
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> Marking as a fix to simplify backporting of the fix
> that follows in the series.
>
> v2:
> - Keep the runtime pm reference over suspend / hibernate and
> document why. (Matt Auld, Rodrigo Vivi):
>
> Fixes: c6a4d46ec1d7 ("drm/xe: evict user memory in PM notifier")
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: <stable@vger.kernel.org> # v6.16+
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/xe/xe_pm.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index a2e85030b7f4..bee9aacd82e7 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -308,17 +308,17 @@ static int xe_pm_notifier_callback(struct notifier_block *nb,
> case PM_SUSPEND_PREPARE:
> xe_pm_runtime_get(xe);
> err = xe_bo_evict_all_user(xe);
> - if (err) {
> + if (err)
> drm_dbg(&xe->drm, "Notifier evict user failed (%d)\n", err);
> - xe_pm_runtime_put(xe);
> - break;
> - }
>
> err = xe_bo_notifier_prepare_all_pinned(xe);
> - if (err) {
> + if (err)
> drm_dbg(&xe->drm, "Notifier prepare pin failed (%d)\n", err);
> - xe_pm_runtime_put(xe);
> - }
> + /*
> + * Keep the runtime pm reference until post hibernation / post suspend to
> + * avoid a runtime suspend interfering with evicted objects or backup
> + * allocations.
> + */
> break;
> case PM_POST_HIBERNATION:
> case PM_POST_SUSPEND:
> @@ -327,9 +327,6 @@ static int xe_pm_notifier_callback(struct notifier_block *nb,
> break;
> }
>
> - if (err)
> - return NOTIFY_BAD;
> -
> return NOTIFY_DONE;
> }
>
next prev parent reply other threads:[~2025-09-02 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 8:38 [PATCH v2 0/3] drm/xe: Fixes around eviction and suspend Thomas Hellström
2025-09-01 8:38 ` [PATCH v2 1/3] drm/xe: Attempt to bring bos back to VRAM after eviction Thomas Hellström
2025-09-02 11:45 ` Matthew Auld
2025-09-01 8:38 ` [PATCH v2 2/3] drm/xe: Allow the pm notifier to continue on failure Thomas Hellström
2025-09-02 10:32 ` Matthew Auld [this message]
2025-09-01 8:38 ` [PATCH v2 3/3] drm/xe: Block exec and rebind worker while evicting for suspend / hibernate Thomas Hellström
2025-09-01 8:45 ` ✓ CI.KUnit: success for drm/xe: Fixes around eviction and suspend (rev2) Patchwork
2025-09-01 9:20 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-01 11:16 ` ✓ Xe.CI.Full: " 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=f16b5123-ed53-45b3-ac13-656ad839e87f@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.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;
as well as URLs for NNTP newsgroup(s).