public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: Borislav Petkov <bp@suse.de>, Terry Bowman <terry.bowman@amd.com>,
	lenb@kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, wei.huang2@amd.com, aros@gmx.com,
	rui.zhang@intel.com
Subject: Re: [PATCH v2] tools/power turbostat: Fix RAPL summary collection on AMD processors
Date: Sat, 24 Apr 2021 09:34:01 +0800	[thread overview]
Message-ID: <20210424013401.GA432412@chenyu-desktop> (raw)
In-Reply-To: <23f75aaf3d37cbad6f8ed7bd970434e4a2dc388e.camel@kepstin.ca>

On Fri, Apr 23, 2021 at 10:00:14AM -0400, Calvin Walton wrote:
> On Fri, 2021-04-23 at 14:19 +0200, Borislav Petkov wrote:
> > On Fri, Apr 23, 2021 at 08:16:07PM +0800, Chen Yu wrote:
> > > From b2e63fe4f02e17289414b4f61237da822df115fb Mon Sep 17 00:00:00
> > > 2001
> > > From: Calvin Walton <calvin.walton@kepstin.ca>
> > > Date: Fri, 23 Apr 2021 17:32:13 +0800
> > > Subject: [PATCH 3/5] tools/power turbostat: Fix offset overflow
> > > issue in index
> > >  converting
> > > 
> > > The idx_to_offset() function returns type int (32-bit signed), but
> > > MSR_PKG_ENERGY_STAT is greater than INT_MAX (or rather, would be
> > > interpreted as a negative number). The end result is that it hits
> > > the if (offset < 0) check in update_msr_sum() resulting in the
> > > timer
> > > callback for updating the stat in the background when long
> > > durations
> > > are used to not happen. The similar issue exists in offset_to_idx()
> > > and update_msr_sum().
> > > 
> > > This patch fixes this issue by converting the 'int' type to 'off_t'
> > > accordingly.
> > > 
> > > Fixes: 9972d5d84d76 ("tools/power turbostat: Enable accumulate RAPL
> > > display")
> > > Signed-off-by: Chen Yu <yu.c.chen@intel.com>
> > 
> > This patch's authorship is weird: it says From: Calvin but doesn't
> > have
> > his SOB here - only yours.
> 
> I think this patch is adapted from one of my earlier submissions? I
> don't think I can really say that I wrote it, but I'll certainly review
> it.
> 
> > 
> > > ---
> > >  tools/power/x86/turbostat/turbostat.c | 10 +++++-----
> > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/tools/power/x86/turbostat/turbostat.c
> > > b/tools/power/x86/turbostat/turbostat.c
> > > index a211264b57fd..77557122b292 100644
> > > --- a/tools/power/x86/turbostat/turbostat.c
> > > +++ b/tools/power/x86/turbostat/turbostat.c
> > > @@ -296,9 +296,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)
> > 
> > And this is silly. MSRs are unsigned int. Fullstop.
> > 
> > So that function should either return u32 or unsigned int or so.
> 
> So, there's two problems with that:
>    1. This function needs to be able to return an error value that cannot be
>       confused with a valid MSR. This is currently done by returning a
>       negative number. If an unsigned value is used, a different way of
>       indicating errors needs to be written.
>    2. We are not using CPU instructions to access MSRs direction. Instead
>       they are being read from /dev/msr. So the "offset" value is actually a
>       seek into the /dev/msr file (using pread), and thus is of type off_t.
>
I see, I misunderstood it with kernel's rdmsr() and ... I'll use the original version.

thanks,
Chenyu
> -- 
> Calvin Walton <calvin.walton@kepstin.ca>
> 

  parent reply	other threads:[~2021-04-24  1:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 19:58 [PATCH v2] tools/power turbostat: Fix RAPL summary collection on AMD processors Terry Bowman
2021-04-19 23:52 ` calvin.walton
2021-04-20  2:03 ` Chen Yu
2021-04-20  8:07   ` Borislav Petkov
2021-04-20 13:15     ` Chen Yu
2021-04-20 13:28       ` Calvin Walton
2021-04-20 14:37         ` Chen Yu
2021-04-20 14:42           ` Calvin Walton
2021-04-23 12:16             ` Chen Yu
2021-04-23 12:19               ` Borislav Petkov
2021-04-23 13:34                 ` Chen Yu
2021-04-23 14:32                   ` Borislav Petkov
2021-04-24  1:14                     ` Chen Yu
2021-04-23 14:00                 ` Calvin Walton
2021-04-23 14:29                   ` Borislav Petkov
2021-04-24  1:34                   ` Chen Yu [this message]
2021-04-23 14:04               ` Calvin Walton
2021-04-23 14:27                 ` Chen Yu
2021-04-23 15:17                   ` Calvin Walton
2021-04-20 14:06       ` Artem S. Tashkinov
2021-04-20 15:25       ` Borislav Petkov
2021-04-23 12:18         ` Chen Yu
2021-04-20 13:32 ` Calvin Walton

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=20210424013401.GA432412@chenyu-desktop \
    --to=yu.c.chen@intel.com \
    --cc=aros@gmx.com \
    --cc=bp@suse.de \
    --cc=calvin.walton@kepstin.ca \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=terry.bowman@amd.com \
    --cc=wei.huang2@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