mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Crofts <crofts@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,  Pavel Machek <pavel@kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Danilo Krummrich <dakr@kernel.org>,
	Johan Hovold <johan@kernel.org>,  Samuel Wu <wusamuel@google.com>
Cc: linux-pm@vger.kernel.org, driver-core@lists.linux.dev,
	 linux-kernel@vger.kernel.org, Joshua Crofts <crofts@kernel.org>
Subject: [PATCH v2 0/2] PM: runtime: add new runtime metrics and summary
Date: Mon, 16 Nov 2026 10:36:08 +0100	[thread overview]
Message-ID: <20261116-pm-runtime-summary-v2-0-a3d8654baf8f@kernel.org> (raw)

Add a new set additional PM runtime metrics to improve power management
debugging and reporting (these metrics may be useful to userspace utilities
such as Powertop).

MOTIVATION:
The current implementation only measures the duration a device spends in
suspended or active mode, which is very limiting. We can't find out how many
times a device changed state or what its shortest suspend cycle was.

This overview would be useful for detecting power "thrashing" and tuning
autosuspend delays. Currently, sysfs only shows the total time a device spent
in active and suspended mode; from an energy standpoint, a continuous 50
second suspension is different from a device cycling 1000 times for 50ms each
(these transitions can be pretty power-hungry). This could help userspace
utilities like PowerTOP to more effectively determine what is causing an
increased power consumption.

NEW FEATURES:
This series introduces the following new metrics:
- resume_count : number of successful transitions to active
- suspend_count: number of successful transitions to suspended
- last_suspended_time: duration of the most recent sleep cycle (ns)
- min_suspended_time / max_suspended_time: shortest and longest sleep
  cycle durations to help detect power thrashing (ns)

By reading the debugfs file /sys/kernel/debug/pm_runtime_summary, you get
the following table describing the power stats of each device with
runtime PM enabled:

Device                           Status        Resumes Suspends   Active(ms)  Suspend(ms)   Last(ms)    Min(ms)    Max(ms)
--------------------------------------------------------------------------------------------------------------------------
0000:00:02.0                     active              1        0        45688            0          0          0          0
0000:00:1f.0                     active              1        0        45687            0          0          0          0
0000:00:1f.2                     active              1        0        45686            0          0          0          0
0000:00:1f.3                     suspended           1        1         1658        44028          0          0          0
00:03:0                          active             15       14        19627        25899         42          5      14811
00:03:0.0                        active             14       13        19626        25900         42          5      14811

TESTING:
Tested with an x86_64 defconfig kernel and QEMU.

AI ASSISTANCE:
Gemini was used to prepare this series.

Signed-off-by: Joshua Crofts <crofts@kernel.org>
---
Changes in v2:
- Drop sysfs patch as it would have a non-negligible impact on boot times and
  the debugfs summary is enough (Samuel Wu)
- Expand cover letter
- Fix Sashiko findings - typo in commit message, race condition, duplicate
  function call
- Link to v1: https://lore.kernel.org/r/20261110-pm-runtime-summary-v1-0-12ebf283db78@kernel.org

---
Joshua Crofts (2):
      PM: runtime: add additional suspend/resume metrics
      PM: runtime: add debugfs entry for pm_runtime_summary

 drivers/base/power/runtime.c | 162 +++++++++++++++++++++++++++++++++++++++++--
 include/linux/pm.h           |  12 ++++
 2 files changed, 169 insertions(+), 5 deletions(-)
---
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
change-id: 20261110-pm-runtime-summary-8dd29a1383bc

Best regards,
-- 
Joshua Crofts <crofts@kernel.org>


             reply	other threads:[~2026-11-16  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  9:36 Joshua Crofts [this message]
2026-11-16  9:36 ` [PATCH v2 1/2] PM: runtime: add additional suspend/resume metrics Joshua Crofts
2026-11-16  9:36 ` [PATCH v2 2/2] PM: runtime: add debugfs entry for pm_runtime_summary Joshua Crofts

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=20261116-pm-runtime-summary-v2-0-a3d8654baf8f@kernel.org \
    --to=crofts@kernel.org \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=wusamuel@google.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

all inboxes | Powered by JetHome®