From: Chen Yu <yu.c.chen@intel.com>
To: youling257 <youling257@gmail.com>, Kurt Garloff <kurt@garloff.de>,
Bingsong Si <owen.si@ucloud.cn>,
"Artem S . Tashkinov" <aros@gmx.com>
Cc: Terry Bowman <terry.bowman@amd.com>,
Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>,
Calvin Walton <calvin.walton@kepstin.ca>,
Borislav Petkov <bp@suse.de>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] tools/power turbostat: Fix offset overflow issue in index converting
Date: Wed, 28 Apr 2021 17:09:16 +0800 [thread overview]
Message-ID: <8167875a1d688b92b0ec707b95855a604afacf01.1619600637.git.yu.c.chen@intel.com> (raw)
In-Reply-To: <cover.1619600637.git.yu.c.chen@intel.com>
From: Calvin Walton <calvin.walton@kepstin.ca>
The idx_to_offset() function returns type int (32-bit signed), but
MSR_PKG_ENERGY_STAT is u32 and would be interpreted as a negative number.
The end result is that it hits the if (offset < 0) check in update_msr_sum()
which prevents the timer callback from updating the stat in the background when
long durations are used. The similar issue exists in offset_to_idx() and
update_msr_sum(). Fix this issue by converting the 'int' to 'off_t' accordingly.
Fixes: 9972d5d84d76 ("tools/power turbostat: Enable accumulate RAPL display")
Signed-off-by: Calvin Walton <calvin.walton@kepstin.ca>
---
tools/power/x86/turbostat/turbostat.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/tools/power/x86/turbostat/turbostat.c b/tools/power/x86/turbostat/turbostat.c
index 37759d6c463d..085057daef86 100644
--- a/tools/power/x86/turbostat/turbostat.c
+++ b/tools/power/x86/turbostat/turbostat.c
@@ -291,9 +291,9 @@ struct msr_sum_array {
/* The percpu MSR sum array.*/
struct msr_sum_array *per_cpu_msr_sum;
-int idx_to_offset(int idx)
+off_t idx_to_offset(int idx)
{
- int offset;
+ off_t offset;
switch (idx) {
case IDX_PKG_ENERGY:
@@ -323,7 +323,7 @@ int idx_to_offset(int idx)
return offset;
}
-int offset_to_idx(int offset)
+int offset_to_idx(off_t offset)
{
int idx;
@@ -3276,7 +3276,7 @@ static int update_msr_sum(struct thread_data *t, struct core_data *c, struct pkg
for (i = IDX_PKG_ENERGY; i < IDX_COUNT; i++) {
unsigned long long msr_cur, msr_last;
- int offset;
+ off_t offset;
if (!idx_valid(i))
continue;
@@ -3285,7 +3285,8 @@ static int update_msr_sum(struct thread_data *t, struct core_data *c, struct pkg
continue;
ret = get_msr(cpu, offset, &msr_cur);
if (ret) {
- fprintf(outf, "Can not update msr(0x%x)\n", offset);
+ fprintf(outf, "Can not update msr(0x%llx)\n",
+ (unsigned long long)offset);
continue;
}
--
2.25.1
next prev parent reply other threads:[~2021-04-28 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 9:08 [PATCH 0/2] tools/power/turbostat: Fix long time duration RAPL calculation Chen Yu
2021-04-28 9:09 ` [PATCH 1/2] tools/power/turbostat: Fix turbostat for AMD Zen CPUs Chen Yu
2021-04-28 9:09 ` Chen Yu [this message]
2021-04-29 19:47 ` [PATCH 0/2] tools/power/turbostat: Fix long time duration RAPL calculation Terry Bowman
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=8167875a1d688b92b0ec707b95855a604afacf01.1619600637.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=aros@gmx.com \
--cc=bas@basnieuwenhuizen.nl \
--cc=bp@suse.de \
--cc=calvin.walton@kepstin.ca \
--cc=kurt@garloff.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=owen.si@ucloud.cn \
--cc=terry.bowman@amd.com \
--cc=youling257@gmail.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;
as well as URLs for NNTP newsgroup(s).