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 21:57:54 +0200 [thread overview]
Message-ID: <20160617195754.GP3912@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.20.1606171539410.21482@macbook-air>
On Fri, Jun 17, 2016 at 03:41:38PM -0400, Vince Weaver wrote:
> FWIW on the trinity machine (F15hM13h) with your patch applied I get the
> following:
>
> vince@a10:~$ sensors
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1: +0.0°C (high = +70.0°C)
> (crit = +70.0°C, hyst = +69.0°C)
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1: N/A (crit = 100.04 W)
Yeah, I didn't expect to be that easy.
Provided hw support on TN is present, someone needs to sit down and
audit the algorithm in show_power() and sanity-check all those values
coming from the PCI regs.
But I'd wait for Rui first to confirm whether it is even worth to chase
this or whether TN is a lost cause because this TDP mechanism is not
supported there or whatever other reason there might be...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-06-17 19:57 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
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 [this message]
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=20160617195754.GP3912@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.