linux-kernel - RE: [RFC PATCH 0/8] EDAC, mce_amd: Add a tracepoint for the decoded error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F61317AB5@ORSMSX114.amr.corp.intel.com>
Date:   Thu, 27 Jul 2017 16:42:19 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>
CC:     linux-edac <linux-edac@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Yazen Ghannam <Yazen.Ghannam@....com>, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH 0/8] EDAC, mce_amd: Add a tracepoint for the decoded
 error

> Later, we could extend that same behavior to Intel for the common
> errors, at least, so that we can dump at least *some* string explaining
> what the error is.

s/common errors/architectural errors/

That means we don't need to keep updating for every Xeon that documents
some MCi_STATUS.MSCOD bits.  Decoding the MCACOD bits will explain
which component is involved (cache, bus, memory) and some detail on the
type of access.

-Tony