[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160224112846.GA3888@pd.tnic>
Date: Wed, 24 Feb 2016 12:28:47 +0100
From: Borislav Petkov <bp@...en8.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
Cc: tony.luck@...el.com, hpa@...or.com, mingo@...hat.com,
tglx@...utronix.de, dougthompson@...ssion.com,
mchehab@....samsung.com, x86@...nel.org,
linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
ashok.raj@...el.com, gong.chen@...ux.intel.com,
len.brown@...el.com, peterz@...radead.org, ak@...ux.intel.com,
alexander.shishkin@...ux.intel.com
Subject: Re: [PATCH 1/4] EDAC, MCE, AMD: Enable error decoding of Scalable
MCA errors
On Tue, Feb 23, 2016 at 04:50:37PM -0600, Aravind Gopalakrishnan wrote:
> Sorry about that. Looks like this pair is not defined in spelling.txt. So,
> might be worth adding there as well?
Oh geez, we have a spelling.txt! I think we can declare the kernel as
done and go do something else with our lives...
> It's the block for programming FUSE registers.
Oh, that's what it is.
So maybe "fuses block" or "fuses" or ... just the capitalized "FUSE" is
kinda misleading.
> How about "Unable to gather IP block that threw the error. Therefore cannot
> decode errors further.\n"
Or simply "Invalid IP block specified, error information is unreliable."
and still continue decoding. It might still be recognizable from the
signature, methinks.
> If for some reason the CPUID bit is not set, then we should not assume the
> processor supports the features right?
Is that even remotely possible? If yes, then we should keep the warning,
otherwise it is useless.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Powered by blists - more mailing lists