mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Max Asbock <masbock@linux.vnet.ibm.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Huang, Ying" <ying.huang@intel.com>,
	"naveen.n.rao@in.ibm.com" <naveen.n.rao@in.ibm.com>,
	"ananth@in.ibm.com" <ananth@in.ibm.com>,
	"lcm@linux.vnet.ibm.com" <lcm@linux.vnet.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] MCE, APEI: Don't enable CMCI when Firmware First mode is set in HEST for corrected machine checks
Date: Sun, 12 May 2013 16:47:08 +0200	[thread overview]
Message-ID: <20130512144708.GA5589@pd.tnic> (raw)
In-Reply-To: <1368208744.4518.182.camel@oc3432500282.ibm.com>

And I was wondering why this is not reaching lkml. Fixed.

On Fri, May 10, 2013 at 10:59:04AM -0700, Max Asbock wrote:
> I'll try to summarize the situation:
> 
> We proposed two iterations of a patch that would parse HEST for a
> Corrected Machine Check entry and cause CMCI to be disabled if the
> Firmware First flag was found to be on in that entry.
> Several shortcomings of this approach were subsequently pointed out:
> a) Disabling CMCI doesn't go far enough. If the firmware wants to
> control corrected machine checks then we shouldn't even be polling the
> MCi_STATUS registers. Therefore we need to disable CMCI and disable
> polling if FF is set.
> 
> b) The firmware may take over only a subset of the possible corrected
> machine check events. If we turn off CMCI (and polling) for all banks we
> may miss out on some types of errors. Therefore we should not
> indiscriminately disable CMCI on all banks.
> 
> The question arose whether the APEI spec allows to specify individual
> machine check banks which fall under FF control. The answer appears to
> be 'possibly'. The Corrected Machine Check (CMC) structure defined in
> the APEI spec allows for a list of Machine Check Bank structures which
> could be used to designate a set of banks falling under FF control.
> However, the spec is silent on how the list of Machine Check Bank
> structures in the CMC structure is be used. 
> 
> Further steps in this endeavor may depend on the interpretation of the
> CMC structure in APEI an whether we can specify individual machine check
> banks that fall under FF control.

Right, so we need a complete solution where all FF banks are excluded
from polling. The question is, does the CMC table in APEI enumerate
*all* FF banks or we need to parse something else too.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

       reply	other threads:[~2013-05-12 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1367881102.4518.68.camel@oc3432500282.ibm.com>
     [not found] ` <20130506232537.GF22041@pd.tnic>
     [not found]   ` <1367897566.4518.83.camel@oc3432500282.ibm.com>
     [not found]     ` <20130507131946.GC7633@pd.tnic>
     [not found]       ` <1367941214.4518.90.camel@oc3432500282.ibm.com>
     [not found]         ` <20130508212237.GI30955@pd.tnic>
     [not found]           ` <3908561D78D1C84285E8C5FCA982C28F2DA47E5E@ORSMSX101.amr.corp.intel.com>
     [not found]             ` <20130508221501.GK30955@pd.tnic>
     [not found]               ` <3908561D78D1C84285E8C5FCA982C28F2DA47F03@ORSMSX101.amr.corp.intel.com>
     [not found]                 ` <1368208744.4518.182.camel@oc3432500282.ibm.com>
2013-05-12 14:47                   ` Borislav Petkov [this message]
2013-06-14 18:17                 ` [PATCH] Re: [Patch] MCE, APEI: Don't enable CMCI when Firmware First mode is set in Naveen N. Rao
2013-06-15 14:48                   ` Borislav Petkov
2013-06-17  7:00                     ` Naveen N. Rao
2013-06-17  7:06                       ` Borislav Petkov
2013-06-17  8:11                         ` Naveen N. Rao
2013-06-17  8:21                           ` Borislav Petkov
2013-06-17 10:31                             ` Naveen N. Rao
2013-06-18  6:43                             ` Naveen N. Rao
2013-06-18 22:29                               ` Tony Luck
2013-06-19  6:58                                 ` Naveen N. Rao
2013-06-16 12:20                   ` Borislav Petkov
2013-06-17  7:00                     ` Naveen N. Rao

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=20130512144708.GA5589@pd.tnic \
    --to=bp@alien8.de \
    --cc=ananth@in.ibm.com \
    --cc=lcm@linux.vnet.ibm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@linux.vnet.ibm.com \
    --cc=naveen.n.rao@in.ibm.com \
    --cc=tony.luck@intel.com \
    --cc=ying.huang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome