Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <matthew.d.roper@intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: [PATCH v3 02/27] drm/xe/pm: Add scope-based cleanup helper for runtime PM
Date: Mon, 17 Nov 2025 19:04:55 -0300	[thread overview]
Message-ID: <176341709502.5989.12881632941364116182@intel.com> (raw)
In-Reply-To: <20251114214335.2388972-31-matthew.d.roper@intel.com>

Quoting Matt Roper (2025-11-14 18:43:38-03:00)
>Add a scope-based helpers for runtime PM that may be used to simplify
>cleanup logic and potentially avoid goto-based cleanup.
>
>For example, using
>
>        guard(xe_pm_runtime)(xe);
>
>will get runtime PM and cause a corresponding put to occur automatically
>when the current scope is exited.  'xe_pm_runtime_noresume' can be used
>as a guard replacement for the corresponding 'noresume' variant.
>There's also an xe_pm_runtime_ioctl conditional guard that can be used
>as a replacement for xe_runtime_ioctl():
>
>        ACQUIRE(xe_pm_runtime_ioctl, pm)(xe);
>        if ((ret = ACQUIRE_ERR(xe_pm_runtime_ioctl, &pm)) < 0)
>                /* failed */
>
>In a few rare cases (such as gt_reset_worker()) we need to ensure that
>runtime PM is dropped when the function is exited by any means
>(including error paths), but the function does not need to acquire
>runtime PM because that has already been done earlier by a different
>function.  For these special cases, an 'xe_pm_runtime_release_only'
>guard can be used to handle the release without doing an acquisition.
>
>These guards will be used in future patches to eliminate some of our
>goto-based cleanup.
>
>v2:
> - Specify success condition for xe_pm runtime_ioctl as _RET >= 0 so
>   that positive values will be properly identified as success and
>   trigger destructor cleanup properly.
>
>v3:
> - Add comments to the kerneldoc for the existing 'get' functions
>   indicating that scope-based handling should be preferred where
>   possible.  (Gustavo)
>
>Cc: Gustavo Sousa <gustavo.sousa@intel.com>
>Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>Signed-off-by: Matt Roper <matthew.d.roper@intel.com>

Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>

>---
> drivers/gpu/drm/xe/xe_pm.c | 21 +++++++++++++++++++++
> drivers/gpu/drm/xe/xe_pm.h | 17 +++++++++++++++++
> 2 files changed, 38 insertions(+)
>
>diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
>index 0e573fb11bbb..ad92a142dc7e 100644
>--- a/drivers/gpu/drm/xe/xe_pm.c
>+++ b/drivers/gpu/drm/xe/xe_pm.c
>@@ -722,6 +722,13 @@ static void xe_pm_runtime_lockdep_prime(void)
> /**
>  * xe_pm_runtime_get - Get a runtime_pm reference and resume synchronously
>  * @xe: xe device instance
>+ *
>+ * When possible, scope-based runtime PM (through guard(xe_pm_runtime)) is
>+ * be preferred over direct usage of this function.  Manual get/put handling
>+ * should only be used when the function contains goto-based logic which
>+ * can break scope-based handling, or when the lifetime of the runtime PM
>+ * reference does not match a specific scope (e.g., runtime PM obtained in one
>+ * function and released in a different one).
>  */
> void xe_pm_runtime_get(struct xe_device *xe)
> {
>@@ -754,6 +761,13 @@ void xe_pm_runtime_put(struct xe_device *xe)
>  * xe_pm_runtime_get_ioctl - Get a runtime_pm reference before ioctl
>  * @xe: xe device instance
>  *
>+ * When possible, scope-based runtime PM (through
>+ * ACQUIRE(xe_pm_runtime_ioctl, ...)) is be preferred over direct usage of this
>+ * function.  Manual get/put handling should only be used when the function
>+ * contains goto-based logic which can break scope-based handling, or when the
>+ * lifetime of the runtime PM reference does not match a specific scope (e.g.,
>+ * runtime PM obtained in one function and released in a different one).
>+ *
>  * Returns: Any number greater than or equal to 0 for success, negative error
>  * code otherwise.
>  */
>@@ -823,6 +837,13 @@ static bool xe_pm_suspending_or_resuming(struct xe_device *xe)
>  * It will warn if not protected.
>  * The reference should be put back after this function regardless, since it
>  * will always bump the usage counter, regardless.
>+ *
>+ * When possible, scope-based runtime PM (through guard(xe_pm_runtime_noresume))
>+ * is be preferred over direct usage of this function.  Manual get/put handling
>+ * should only be used when the function contains goto-based logic which can
>+ * break scope-based handling, or when the lifetime of the runtime PM reference
>+ * does not match a specific scope (e.g., runtime PM obtained in one function
>+ * and released in a different one).
>  */
> void xe_pm_runtime_get_noresume(struct xe_device *xe)
> {
>diff --git a/drivers/gpu/drm/xe/xe_pm.h b/drivers/gpu/drm/xe/xe_pm.h
>index f7f89a18b6fc..6b27039e7b2d 100644
>--- a/drivers/gpu/drm/xe/xe_pm.h
>+++ b/drivers/gpu/drm/xe/xe_pm.h
>@@ -6,6 +6,7 @@
> #ifndef _XE_PM_H_
> #define _XE_PM_H_
> 
>+#include <linux/cleanup.h>
> #include <linux/pm_runtime.h>
> 
> #define DEFAULT_VRAM_THRESHOLD 300 /* in MB */
>@@ -37,4 +38,20 @@ int xe_pm_block_on_suspend(struct xe_device *xe);
> void xe_pm_might_block_on_suspend(void);
> int xe_pm_module_init(void);
> 
>+static inline void __xe_pm_runtime_noop(struct xe_device *xe) {}
>+
>+DEFINE_GUARD(xe_pm_runtime, struct xe_device *,
>+             xe_pm_runtime_get(_T), xe_pm_runtime_put(_T))
>+DEFINE_GUARD(xe_pm_runtime_noresume, struct xe_device *,
>+             xe_pm_runtime_get_noresume(_T), xe_pm_runtime_put(_T))
>+DEFINE_GUARD_COND(xe_pm_runtime, _ioctl, xe_pm_runtime_get_ioctl(_T), _RET >= 0)
>+
>+/*
>+ * Used when a function needs to release runtime PM in all possible cases
>+ * and error paths, but the wakeref was already acquired by a different
>+ * function (i.e., get() has already happened so only a put() is needed).
>+ */
>+DEFINE_GUARD(xe_pm_runtime_release_only, struct xe_device *,
>+             __xe_pm_runtime_noop(_T), xe_pm_runtime_put(_T));
>+
> #endif
>-- 
>2.51.1
>

  reply	other threads:[~2025-11-17 22:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 21:43 [PATCH v3 00/27] Scope-based forcewake and runtime PM Matt Roper
2025-11-14 21:43 ` [PATCH v3 01/27] drm/xe/forcewake: Add scope-based cleanup for forcewake Matt Roper
2025-11-17 22:03   ` Gustavo Sousa
2025-11-17 22:17     ` Gustavo Sousa
2025-11-14 21:43 ` [PATCH v3 02/27] drm/xe/pm: Add scope-based cleanup helper for runtime PM Matt Roper
2025-11-17 22:04   ` Gustavo Sousa [this message]
2025-11-14 21:43 ` [PATCH v3 03/27] drm/xe/gt: Use scope-based cleanup Matt Roper
2025-11-14 21:43 ` [PATCH v3 04/27] drm/xe/gt_idle: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 05/27] drm/xe/guc: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 06/27] drm/xe/guc_pc: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 07/27] drm/xe/mocs: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 08/27] drm/xe/pat: Use scope-based forcewake Matt Roper
2025-11-14 21:43 ` [PATCH v3 09/27] drm/xe/pxp: Use scope-based cleanup Matt Roper
2025-11-14 21:43 ` [PATCH v3 10/27] drm/xe/gsc: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 11/27] drm/xe/device: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 12/27] drm/xe/devcoredump: " Matt Roper
2025-11-17 22:09   ` Gustavo Sousa
2025-11-14 21:43 ` [PATCH v3 13/27] drm/xe/display: Use scoped-cleanup Matt Roper
2025-11-17 22:11   ` Gustavo Sousa
2025-11-14 21:43 ` [PATCH v3 14/27] drm/xe: Return forcewake reference type from force_wake_get_any_engine() Matt Roper
2025-11-17 22:19   ` Gustavo Sousa
2025-11-14 21:43 ` [PATCH v3 15/27] drm/xe/drm_client: Use scope-based cleanup Matt Roper
2025-11-17 22:28   ` Gustavo Sousa
2025-11-14 21:43 ` [PATCH v3 16/27] drm/xe/gt_debugfs: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 17/27] drm/xe/huc: Use scope-based forcewake Matt Roper
2025-11-14 21:43 ` [PATCH v3 18/27] drm/xe/query: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 19/27] drm/xe/reg_sr: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 20/27] drm/xe/vram: " Matt Roper
2025-11-14 21:43 ` [PATCH v3 21/27] drm/xe/bo: Use scope-based runtime PM Matt Roper
2025-11-14 21:43 ` [PATCH v3 22/27] drm/xe/ggtt: Use scope-based runtime pm Matt Roper
2025-11-14 21:43 ` [PATCH v3 23/27] drm/xe/hwmon: Use scope-based runtime PM Matt Roper
2025-11-14 21:44 ` [PATCH v3 24/27] drm/xe/sriov: " Matt Roper
2025-11-14 21:44 ` [PATCH v3 25/27] drm/xe/tests: " Matt Roper
2025-11-14 21:44 ` [PATCH v3 26/27] drm/xe/sysfs: Use scope-based runtime power management Matt Roper
2025-11-14 21:44 ` [PATCH v3 27/27] drm/xe/debugfs: Use scope-based runtime PM Matt Roper
2025-11-14 23:22 ` ✗ CI.checkpatch: warning for Scope-based forcewake and runtime PM (rev4) Patchwork
2025-11-14 23:23 ` ✓ CI.KUnit: success " Patchwork
2025-11-15  0:14 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-15 11:18 ` ✗ Xe.CI.Full: failure " 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=176341709502.5989.12881632941364116182@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@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