[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F2DA881C2@ORSMSX106.amr.corp.intel.com>
Date: Wed, 19 Jun 2013 19:05:16 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
"ananth@...ibm.com" <ananth@...ibm.com>,
"masbock@...ux.vnet.ibm.com" <masbock@...ux.vnet.ibm.com>,
"lcm@...ux.vnet.ibm.com" <lcm@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [PATCH v2 2/2] mce: acpi/apei: Add a boot option to disable ff
mode for corrected errors
> Why, fill out struct mce and do mce_log(mce) does not suffice?
There is (or should be) a lot more interesting stuff in the CPER than just the address. Stuff
that we don't have fields for in the existing mcelog structure. We also need to treat filtered
records from modern APEI implementations a bit differently from the old stuff. The original
user of this code was Westmere-EX, which used it as a workaround for a missing address in
MCi_ADDR for corrected errors. So in that scenario we had every error being reported and
mcelog(8) deamon doing the threshold analysis to decide when to take action.
In this new modern world - Naveen wants to have the BIOS decide the threshold, so we'd
like Linux to take some action as soon as it sees just one CPER.
-Tony
Powered by blists - more mailing lists