From: Huang Rui <ray.huang@amd.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
Robert Richter <rric@kernel.org>,
"Jacob Shin" <jacob.w.shin@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@intel.com>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Borislav Petkov <bp@alien8.de>,
Guenter Roeck <linux@roeck-us.net>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [REDO PATCH v7] perf/x86/amd/power: Add AMD accumulated power reporting mechanism
Date: Fri, 17 Jun 2016 18:03:07 +0800 [thread overview]
Message-ID: <20160617100306.GB13900@hr-amur2> (raw)
In-Reply-To: <alpine.DEB.2.20.1606161636530.2744@macbook-air>
On Thu, Jun 16, 2016 at 04:44:20PM -0400, Vince Weaver wrote:
> On Thu, 16 Jun 2016, Huang Rui wrote:
>
> > > 1. In theory this should also work on an amd fam16h model 30h
> > > processor too, correct? The current code limits things to fam15h
> > > even though the fam16mod30h has all the proper cpuid flags.
> > >
> >
> > I was told this feature would be supported on fam15h 60h, 70h and
> > later processors before. Just checked the fam16h model 30h BKDG, yes,
> > it should be also supported. But I didn't test that platform, if you
> > confirm it works in your side. We can enable it.
>
> I can confirm I get power readings on my fam16hmod30h board once I apply a
> trivial patch to the driver. I'll send the patch in a separate e-mail.
>
OK, thanks.
> > PTSC's frequency is about 100Mhz, it shouldn't be overflow.
>
> That's what I thought. I'm trying to read the value using the /dev/msr
> interface from userspace and I get weird results.
>
> i.e.:
> Jx: read 62d299b84
> PTSC MSR: read 72fe92
>
> sleep 5ms
>
> Jy: read 631b453b9
> PTSC MSR: read 46b25
>
> this happens about half the time (PTSC going backwards). Though
> admittedly the problem could somehow be in the MSR code I'm using.
>
Can you try to read the MSR value two times with the same core
(rdmsrl_on_cpu)?
Thanks,
Rui
next prev parent reply other threads:[~2016-06-17 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 5:45 [REDO PATCH v7] perf/x86/amd/power: Add AMD accumulated power reporting mechanism Huang Rui
2016-03-21 9:55 ` [tip:perf/urgent] " tip-bot for Huang Rui
2016-06-16 1:13 ` [REDO PATCH v7] " Vince Weaver
2016-06-16 5:38 ` Huang Rui
2016-06-16 5:59 ` Huang Rui
2016-06-16 21:10 ` Vince Weaver
2016-06-16 21:16 ` Vince Weaver
2016-06-16 21:36 ` Borislav Petkov
2016-06-16 16:47 ` Borislav Petkov
2016-06-17 9:58 ` Huang Rui
2016-07-19 18:22 ` Vince Weaver
2016-07-20 2:58 ` Huang Rui
2016-06-16 20:44 ` Vince Weaver
2016-06-17 10:03 ` Huang Rui [this message]
2016-06-17 15:54 ` Vince Weaver
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=20160617100306.GB13900@hr-amur2 \
--to=ray.huang@amd.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=fengguang.wu@intel.com \
--cc=jacob.w.shin@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rric@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
--cc=x86@kernel.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 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).