RE: [Patch] MCE, APEI: Don't enable CMCI when Firmware First mode is set in HEST for corrected machine checks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Because if yes, you won't need any of the HEST header parsing here. So
> what's up?

I think[1] HEST can tell you which banks report using APEI (as well as/instead of) CMCI.

So a full solution should take into account lots of possibilities:

1) Some banks may not support CMCI at all (bit 30 in MCi_CTL2 register ignores attempts to enable). For these banks Linux should poll.
2) BIOS may support generation of APEI records for certain classes of errors. HEST will say which banks are affected, and if we prefer APEI, we should disable CMCI for these banks (and not poll them).
3) Some banks may support CMCI, but don't have BIOS support to generate APEI records.  We should continue to enable CMCI for these.

We should also take advantage of more information provided in the APEI record.  We only look at mem_err->physical_addr for memory errors - but there are a ton of other potentially interesting things in there.

-Tony

[1] But I may be misreading ACPI spec - unfortunately it just has descriptions of *what* bits do, but no rationale as to *why* anyone would want to use them, or tradeoffs between different operating modes. Willing to be re-educated if this is all horribly wrong.
��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f





[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux