From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-gfx@lists.freedesktop.org, vinay.belgaumkar@intel.com
Cc: dev@lankhorst.se
Subject: [PATCH 0/3] Fixup deadlock scenarios in the PMU path
Date: Tue, 29 Sep 2026 12:01:48 -0700 [thread overview]
Message-ID: <20260929190147.2886670-5-umesh.nerlige.ramappa@intel.com> (raw)
Based on one user report bug regarding a deadlock in the
guc_engine_busyness path, this series fixes such scenarios.
v2:
- Disable pmu on PREEMPT_RT kernels
- Review comments from v1
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Maarten Lankhorst (1):
drm/i915/pmu: Disable on PREEMPT_RT
Umesh Nerlige Ramappa (2):
drm/i915/guc: Use a delayed wakeref put in guc_engine_busyness()
drm/i915/pmu: Use a delayed wakeref put in get_rc6()
drivers/gpu/drm/i915/gt/intel_gt_pm.h | 24 +++++++++++++++++++
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 7 +++++-
drivers/gpu/drm/i915/i915_pmu.c | 21 +++++++++++++++-
3 files changed, 50 insertions(+), 2 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-29 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 19:01 Umesh Nerlige Ramappa [this message]
2026-09-29 19:01 ` [PATCH 1/3] drm/i915/pmu: Disable on PREEMPT_RT Umesh Nerlige Ramappa
2026-09-30 5:42 ` Maarten Lankhorst
2026-09-30 8:02 ` Tvrtko Ursulin
2026-09-30 13:25 ` Maarten Lankhorst
2026-10-01 12:15 ` Tvrtko Ursulin
2026-09-29 19:01 ` [PATCH 2/3] drm/i915/guc: Use a delayed wakeref put in guc_engine_busyness() Umesh Nerlige Ramappa
2026-09-29 19:01 ` [PATCH 3/3] drm/i915/pmu: Use a delayed wakeref put in get_rc6() Umesh Nerlige Ramappa
2026-09-29 21:35 ` ✓ i915.CI.BAT: success for Fixup deadlock scenarios in the PMU path (rev2) Patchwork
2026-09-30 7:26 ` ✗ i915.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=20260929190147.2886670-5-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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