From: Shuah Khan <skhan@linuxfoundation.org>
To: "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B . Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] pm: cpupower: Couple of fixes to the cpupower monitor
Date: Wed, 18 Jun 2025 16:43:44 -0600 [thread overview]
Message-ID: <d3e1b43a-48f6-46eb-be53-4731e5eb5681@linuxfoundation.org> (raw)
In-Reply-To: <20250612122355.19629-1-gautham.shenoy@amd.com>
On 6/12/25 06:23, Gautham R. Shenoy wrote:
> Hello!
>
> This patch-series contains a couple of fixes to the cpupower monitor.
>
> * The first patch ensures that the C0% printed by the mperf-monitor is
> 100% when the core is fully busy.
>
> * The second patch ensure that the CORE and CPU fields are printed in
> the cpupower-monitor output for multi-socket systems. This has been
> broken since 6.15.
>
> Gautham R. Shenoy (2):
> pm: cpupower: Fix the snapshot-order of tsc,mperf, clock in mperf_stop()
> pm: cpupower: Fix printing of CORE, CPU fields in cpupower-monitor
>
> tools/power/cpupower/utils/idle_monitor/cpupower-monitor.c | 4 ----
> tools/power/cpupower/utils/idle_monitor/mperf_monitor.c | 4 ++--
> 2 files changed, 2 insertions(+), 6 deletions(-)
>
Applied - will include in my fixes PR to Rafael
https://web.git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git/?h=cpupower
thanks,
-- Shuah
prev parent reply other threads:[~2025-06-18 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 12:23 Gautham R. Shenoy
2025-06-12 12:23 ` [PATCH 1/2] pm: cpupower: Fix the snapshot-order of tsc,mperf, clock in mperf_stop() Gautham R. Shenoy
2025-06-12 12:23 ` [PATCH 2/2] pm: cpupower: Fix printing of CORE, CPU fields in cpupower-monitor Gautham R. Shenoy
2025-06-18 22:43 ` Shuah Khan [this message]
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=d3e1b43a-48f6-46eb-be53-4731e5eb5681@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gautham.shenoy@amd.com \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=trenn@suse.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®