From: Borislav Petkov <bp@amd64.org>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, H Peter Anvin <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
"Brown, Len" <len.brown@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] x86/mcheck/therm_throt.c: Don't log power limit and package level thermal throttle event in mce log
Date: Tue, 6 Dec 2011 20:06:48 +0100 [thread overview]
Message-ID: <20111206190648.GB20445@aftab> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F075501A22B5365@orsmsx508.amr.corp.intel.com>
On Tue, Dec 06, 2011 at 09:48:41AM -0800, Yu, Fenghua wrote:
> The printk is one way to notify users about the power limit and
> thermal throttle. The printk only dumps the events in an interval
> (300*HZ).
>
> Another way is to count the events in
> /sys/devices/system/cpu/cpu#/thermal_throttle. In this way, kernel
> logs every interrupt on any cpu into respective counters. User
> application can poll the counters and get more accurate and timely
> information for the events.
>
> As explained in this patch, core level thermal throttle is still
> logged in mcelog for legacy reason after this patch is applied.
I can see all that. Still, I'm questioning the need for those printks. A
user application polling the counters is a much better solution, IMHO,
than spamming the logs. IOW, is there a strong reason to have this -
even ratelimited - information in the logs and unnerve users, or, would
it be better to collect this info somewhere queitly and present it only
when something requests it?
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2011-12-06 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 21:11 [PATCH] x86/mcheck/therm_throt.c: Don't log power limit and package level thermal throttle event in mce log Fenghua Yu
2011-12-05 13:18 ` Borislav Petkov
2011-12-05 22:18 ` Luck, Tony
2011-12-06 15:31 ` Borislav Petkov
2011-12-06 17:48 ` Yu, Fenghua
2011-12-06 19:06 ` Borislav Petkov [this message]
2011-12-06 19:26 ` Tony Luck
2011-12-06 19:56 ` Borislav Petkov
2011-12-06 19:27 ` Yu, Fenghua
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=20111206190648.GB20445@aftab \
--to=bp@amd64.org \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 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.