[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F4A57D0@ORSMSX115.amr.corp.intel.com>
Date: Thu, 17 Oct 2019 21:31:30 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>
CC: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"bberg@...hat.com" <bberg@...hat.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hdegoede@...hat.com" <hdegoede@...hat.com>,
"ckellner@...hat.com" <ckellner@...hat.com>
Subject: RE: [PATCH 1/2] x86, mce, therm_throt: Optimize logging of thermal
throttle messages
>> That all sounds like the printk should be downgraded too, it is not a
>> KERN_CRIT warning. It is more a notification that we're getting warm.
>
> Right, and I think we should take Benjamin's patch after all - perhaps
> even tag it for stable if that message is annoying people too much - and
> Srinivas can do the dynamic thing ontop.
That sounds like the right short term action.
Depending on what we end up with from Srinivas ... we may want
to reconsider the severity. The basic premise of Srinivas' patch
is to avoid printing anything for short excursions above temperature
threshold. But the effect of that is that when we find the core/package
staying above temperature for an extended period of time, we are
in a serious situation where some action may be needed. E.g.
move the laptop off the soft surface that is blocking the air vents.
-Tony
Powered by blists - more mailing lists