From: Borislav Petkov <bp@alien8.de>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Huang Rui <ray.huang@amd.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [patch] events/amd/power add support for fam16h model30h
Date: Fri, 17 Jun 2016 18:27:28 +0200 [thread overview]
Message-ID: <20160617162728.GC3912@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.20.1606171154340.20990@macbook-air>
On Fri, Jun 17, 2016 at 11:56:31AM -0400, Vince Weaver wrote:
> Has anyone actually verified that the fam15h excavator machines are
> producing "stable" results?
Not that I know of. Rui, any ideas?
> I know on my fam15h piledriver machines the results returned by the
> drivers/hwmon/fam15h_power.c driver look questionable at best, which
> is what started my trying to figure this whole thing out in the first
> place.
Piledriver? What f/m/s is that?
Because I have a PD here - AMD FX(tm)-8350 Eight-Core Processor -
F15hM02 and sensors gives only this below. But my PD doesn't have
X86_FEATURE_ACC_POWER.
$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +18.4°C (high = +70.0°C)
(crit = +90.0°C, hyst = +87.0°C)
fam15h_power-pci-00c4
Adapter: PCI adapter
power1: 19.38 W (crit = 125.19 W)
radeon-pci-0100
Adapter: PCI adapter
temp1: +85.0°C
---
Do you mean this PCI adapter thing?
I can get it right up to crit when building a kernel:
power1: 124.76 W (crit = 125.19 W)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-06-17 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 21:00 [patch] events/amd/power add support for fam16h model30h Vince Weaver
2016-06-16 21:12 ` Borislav Petkov
2016-06-17 10:07 ` Huang Rui
2016-06-17 10:31 ` Borislav Petkov
2016-06-17 15:56 ` Vince Weaver
2016-06-17 16:27 ` Borislav Petkov [this message]
2016-06-17 17:38 ` Vince Weaver
2016-06-17 18:19 ` Borislav Petkov
2016-06-17 18:58 ` Vince Weaver
2016-06-17 19:41 ` Vince Weaver
2016-06-17 19:57 ` Borislav Petkov
2016-06-17 19:51 ` Borislav Petkov
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=20160617162728.GC3912@pd.tnic \
--to=bp@alien8.de \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ray.huang@amd.com \
--cc=vincent.weaver@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.