From: Nitin Gote <nitin.r.gote@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Nitin Gote <nitin.r.gote@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: [PATCH] drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug
Date: Thu, 6 Aug 2026 14:27:12 +0530 [thread overview]
Message-ID: <20260806085711.437110-2-nitin.r.gote@intel.com> (raw)
Exec queues are owned by user fds and are destroyed when the fd is closed.
After hot-unplug this can happen from a deferred close during process
exit, after the device has been removed and runtime PM has been disabled.
The queue destroy path can call xe_pm_runtime_get_noresume(), and since
runtime PM is disabled pm_runtime_get_if_in_use() returns no reference,
so it warns about "Missing outer runtime PM protection".
This is a false positive for the hot-unplug teardown case. The device is
already unplugged, and the queue destroy path that triggered this warning
was checked and does not touch hardware state after unplug. GuC has already
been sanitized by guc_fini_hw(), so no H2G is sent and the hardware
teardown path is no longer reachable.
Skip the warning when the DRM device is already unplugged.
Observed with new IGT core_hotunplug subtests:
igt@core_hotunplug@hotreplug-with-load
igt@core_hotunplug@hotunplug-rescan-with-load
v2:
- Drop the drm_dev_is_unplugged() bypass from guc_exec_queue_destroy()
and instead exclude hot-unplug from the WARN in
xe_pm_runtime_get_noresume(). (Matthew Brost)
v3:
- Clarify that the queue destroy path was checked and does not touch
hardware state after unplug. (Matthew Auld)
Link: https://patchwork.freedesktop.org/patch/725773/?series=166744&rev=4
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Assisted-by: GitHub-Copilot:claude-opus-4.8
Signed-off-by: Nitin Gote <nitin.r.gote@intel.com>
---
drivers/gpu/drm/xe/xe_pm.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
index a5289a9df8d2..a038687d5b2c 100644
--- a/drivers/gpu/drm/xe/xe_pm.c
+++ b/drivers/gpu/drm/xe/xe_pm.c
@@ -10,6 +10,7 @@
#include <linux/suspend.h>
#include <linux/dmi.h>
+#include <drm/drm_drv.h>
#include <drm/drm_managed.h>
#include <drm/ttm/ttm_placement.h>
@@ -914,7 +915,9 @@ void xe_pm_runtime_get_noresume(struct xe_device *xe)
if (!ref) {
pm_runtime_get_noresume(xe->drm.dev);
- drm_WARN(&xe->drm, !xe_pm_suspending_or_resuming(xe),
+ drm_WARN(&xe->drm,
+ !drm_dev_is_unplugged(&xe->drm) &&
+ !xe_pm_suspending_or_resuming(xe),
"Missing outer runtime PM protection\n");
}
}
--
2.50.1
next reply other threads:[~2026-08-06 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:57 Nitin Gote [this message]
2026-08-06 8:30 ` [PATCH] drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug Raag Jadav
2026-08-06 9:38 ` Matthew Brost
2026-08-06 19:01 ` Matthew Brost
2026-08-07 13:38 ` Gote, Nitin R
2026-08-07 18:39 ` Matthew Brost
2026-08-06 8:56 ` ✓ CI.KUnit: success for drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug (rev2) Patchwork
2026-08-06 9:52 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-06 18:39 ` ✗ Xe.CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 5:36 [PATCH] drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug Nitin Gote
2026-07-30 5:59 ` Raag Jadav
2026-07-30 12:05 ` Gote, Nitin R
2026-07-30 12:31 ` Raag Jadav
2026-08-06 6:09 ` Gote, Nitin R
2026-08-06 6:27 ` Raag Jadav
2026-07-30 12:35 ` Matthew Auld
2026-08-06 6:10 ` Gote, Nitin R
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=20260806085711.437110-2-nitin.r.gote@intel.com \
--to=nitin.r.gote@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