[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F4A6045@ORSMSX115.amr.corp.intel.com>
Date: Thu, 17 Oct 2019 23:53:18 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: Peter Zijlstra <peterz@...radead.org>,
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
> * we throttle the machine from within the kernel - whatever that may mean
> * if that doesn't help, we stop scheduling !root tasks
> * if that doesn't help, we halt
The silicon will do that "halt" step all by itself if the temperature
continues to rise and hits the highest of the temperature thresholds.
-Tony
Powered by blists - more mailing lists