From: Shuah Khan <skhan@linuxfoundation.org>
To: He Rongguang <herongguang@linux.alibaba.com>,
trenn@suse.com, shuah@kernel.org, jwyatt@redhat.com,
jkacur@redhat.com, wyes.karny@amd.com
Cc: linux-kernel@vger.kernel.org, shannon.zhao@linux.alibaba.com,
linux-pm@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] cpupower: fix TSC MHz calculation for Mperf monitor
Date: Mon, 9 Dec 2024 17:43:33 -0700 [thread overview]
Message-ID: <e5b0996d-be80-47a9-af28-ee9776638ab7@linuxfoundation.org> (raw)
In-Reply-To: <269b8bb2-85b5-4cc9-9354-a1270f2eed35@linux.alibaba.com>
On 11/28/24 02:50, He Rongguang wrote:
> Commit 'cpupower: Make TSC read per CPU for Mperf monitor' (c2adb1877b7)
> changes TSC counter reads to per cpu, but left time diff global (from
> start of all cpus to end of all cpus), thus diff(time) is too large for
> a cpu's tsc counting, resulting in far less than acutal TSC_Mhz and thus
> `cpupower monitor` showing far less than actual cpu realtime frequency.
>
> Fix this by making timediff also per cpu.
>
> /proc/cpuinfo shows frequency:
> cat /proc/cpuinfo | egrep -e 'processor' -e 'MHz'
> ...
> processor : 171
> cpu MHz : 4108.498
> ...
>
> before fix (System 100% busy):
> | Mperf || Idle_Stats
> CPU| C0 | Cx | Freq || POLL | C1 | C2
> 171| 0.77| 99.23| 2279|| 0.00| 0.00| 0.00
>
> after fix (System 100% busy):
> | Mperf || Idle_Stats
> CPU| C0 | Cx | Freq || POLL | C1 | C2
> 171| 0.46| 99.54| 4095|| 0.00| 0.00| 0.00
>
> Fixes: c2adb1877b76f ("cpupower: Make TSC read per CPU for Mperf monitor")
> Signed-off-by: He Rongguang <herongguang@linux.alibaba.com>
> ---
This patch has several warnings and seems to corrupt. Can you
look into this and send v2?
scripts/checkpatch.pl will show you the problems.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-12-10 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 9:50 He Rongguang
2024-12-02 2:21 ` He Rongguang
2024-12-10 0:43 ` Shuah Khan [this message]
2024-12-11 3:22 ` He Rongguang
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=e5b0996d-be80-47a9-af28-ee9776638ab7@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=herongguang@linux.alibaba.com \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shannon.zhao@linux.alibaba.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
--cc=wyes.karny@amd.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®