From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org,
yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH] x86/mce: Cover grading of AMD machine error checks
Date: Fri, 11 Mar 2022 08:07:23 -0600 [thread overview]
Message-ID: <18a5a49a-e68f-621e-f8ae-16e794a74905@amd.com> (raw)
In-Reply-To: <Yip4EV69+lElCuPM@zn.tnic>
On 3/10/2022 4:13 PM, Borislav Petkov wrote:
> On Thu, Mar 10, 2022 at 12:24:08PM -0600, Carlos Bilbao wrote:
>> We will cover grading of MCEs like deferred memory scrub errors, attempts
>> to access poisonous data, etc. I could list all new covered cases in the
>> commit message if you think that'd be positive.
>
> So no actual use case - you want to grade error severity for all types
> of MCEs.
>
>> Hope that helps clarify,
>
> Yes, it does a bit.
>
> It sounds to me like you want to do at least two patches:
>
> 1. Extend the severity grading function with the new types of errors
>
> 2. Add string descriptions of the error types mce_severity_amd() looks
> at, so that mce_panic() issues them.
>
> I.e., you want to decode the fatal MCEs which panic the machine.
>
> In general, what would help is if you think about what you're trying to
> achieve and write it down first. How to achieve that we can figure out
> later.
>
> What happens now is you send me a patch and I'm trying to decipher from
> the code why you're doing what you're doing. Which is kinda backwards if
> you think about it...
>
Glad we are on the same page now. I will prepare a pachset and include more
informative commit messages.
Thanks,
Carlos
prev parent reply other threads:[~2022-03-11 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:41 [PATCH] x86/mce: Cover grading of AMD machine error checks Carlos Bilbao
2022-03-09 18:37 ` Borislav Petkov
2022-03-10 18:24 ` Carlos Bilbao
2022-03-10 22:13 ` Borislav Petkov
2022-03-11 14:07 ` Carlos Bilbao [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=18a5a49a-e68f-621e-f8ae-16e794a74905@amd.com \
--to=carlos.bilbao@amd.com \
--cc=bilbao@vt.edu \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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