From: "Luck, Tony" <tony.luck@intel.com>
To: Steve Wahl <steve.wahl@hpe.com>
Cc: Kyle Meyer <kyle.meyer@hpe.com>,
russ.anderson@hpe.com, bp@alien8.de, linux-edac@vger.kernel.org
Subject: Re: [PATCH] x86/MCE: Set the MCE's status and misc members
Date: Fri, 7 Aug 2020 09:33:51 -0700 [thread overview]
Message-ID: <20200807163351.GA28961@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20200807150548.GK4686@localhost.localdomain>
On Fri, Aug 07, 2020 at 10:05:50AM -0500, Steve Wahl wrote:
> There's one small code change I suggest below.
>
> But now it's time to think about the description. We need to zoom out
> to the 10,000 ft. view. IMHO, to understand what this patch does,
> your current description requires the reader to be more familiar with
> the involved functions than we should expect.
Maybe also travel back in time to why apei_mce_report_mem_error()
was created in the first place.
This was a workaround for a couple of Intel CPUs (Nehalem, Westmere)
that didn't provide a system address in MCi_ADDR. Since BIOS could figure
out the address, it was tasked with reporting to the OS suing APEI.
apei_mce_report_mem_error() did the minimum necessary to create
an error log that mcelog(8) daemon could process.
Jump forward in time to Sandybridge (and all successors) and the
reason for the workaround is gone. All of them provide a system
address in the machine check bank ... so this APEI path is a
poor substitute for getting the data from the machine check bank
(which will give you the channel, the corrected error count, and
perhaps other useful information).
So why are we applying band-aids to this decade old workaround?
-Tony
prev parent reply other threads:[~2020-08-07 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:27 [PATCH] x86/MCE: Set the MCE's status and misc members Kyle Meyer
2020-08-07 14:41 ` Borislav Petkov
2020-08-07 15:05 ` Steve Wahl
2020-08-07 16:33 ` Luck, Tony [this message]
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=20200807163351.GA28961@agluck-desk2.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=kyle.meyer@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.