From: Thomas Renninger <trenn@suse.com>
To: linux-pm@vger.kernel.org
Cc: skhan@linuxfoundation.org
Subject: [PATCH 0/2] Introduce powercap userspace frontend
Date: Sat, 09 Jul 2022 10:13:27 +0200 [thread overview]
Message-ID: <4954139.fJS9391jLT@c100> (raw)
cpupower powercap-info
cpupower monitor -m RAPL
further development could provide:
cpupower powercap-set
to enable/disable RAPL domains, etc.
Thomas Renninger (2):
cpupower: Introduce powercap intel-rapl library helpers and
powercap-info command
cpupower: rapl monitor - shows the used power consumption in uj for
each rapl domain
tools/power/cpupower/Makefile | 12 +-
tools/power/cpupower/lib/powercap.c | 290 ++++++++++++++++++
tools/power/cpupower/lib/powercap.h | 54 ++++
.../cpupower/man/cpupower-powercap-info.1 | 25 ++
tools/power/cpupower/utils/builtin.h | 2 +
tools/power/cpupower/utils/cpupower.c | 1 +
.../utils/idle_monitor/cpupower-monitor.c | 7 +-
.../utils/idle_monitor/idle_monitors.def | 1 +
.../utils/idle_monitor/rapl_monitor.c | 141 +++++++++
tools/power/cpupower/utils/powercap-info.c | 113 +++++++
10 files changed, 639 insertions(+), 7 deletions(-)
create mode 100644 tools/power/cpupower/lib/powercap.c
create mode 100644 tools/power/cpupower/lib/powercap.h
create mode 100644 tools/power/cpupower/man/cpupower-powercap-info.1
create mode 100644 tools/power/cpupower/utils/idle_monitor/rapl_monitor.c
create mode 100644 tools/power/cpupower/utils/powercap-info.c
--
2.33.0
next reply other threads:[~2022-07-09 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 8:13 Thomas Renninger [this message]
2022-07-20 9:45 ` [PATCH 0/2] Introduce powercap userspace frontend Zhang Rui
2022-07-21 13:02 ` Thomas Renninger
-- strict thread matches above, loose matches on Subject: below --
2022-11-23 11:18 Thomas Renninger
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=4954139.fJS9391jLT@c100 \
--to=trenn@suse.com \
--cc=linux-pm@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.