From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"slaoub@gmail.com" <slaoub@gmail.com>,
"luto@amacapital.net" <luto@amacapital.net>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH] x86, mce, severities: Add AMD severities function
Date: Fri, 20 Mar 2015 10:59:33 -0500 [thread overview]
Message-ID: <550C43E5.4090302@amd.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32A23E9C@ORSMSX114.amr.corp.intel.com>
On 3/19/2015 12:15 PM, Luck, Tony wrote:
>>> It would be best if what Tony suggested comes ontop of your patch with
>>> his Suggested-by: tag. This ordering should be also the easiest wrt
>>> functionality and bisectability.
>>>
>>>
>> Ok, I'll have it ready and send out a V2 by tomorrow if there are no
>> other comments/reviews.
> Fame & glory ... whatever. Just be sure to make the _intel() and _amd()
> severity functions "static" ... so you'll need something like this in mce-severity.c
>
> void mce_vendor_severity_init(void)
> {
> .... assign mce_severity here
> }
>
>
Ok, Here's how I have it currently:
void __init mcheck_vendor_init_severity(void)
{
struct cpuinfo_x86 *c = &boot_cpu_data;
switch (c->x86_vendor) {
case X86_VENDOR_INTEL:
mce_severity = mce_severity_intel;
break;
case X86_VENDOR_AMD:
mce_severity = mce_severity_amd;
break;
default:
break;
}
}
And I call this from mcheck_init().
I tested the above bits on AMD and the severities grading works fine.
Should we also come up with a '_default' function to assign to
mce_severity function pointer?
Something like-
static int mce_severity_default(struct mce *m, int tolerant,
char **msg, bool is_excp)
{
pr_err("CPU#%d: No vendor specific severities grader assigned.
Implementing default grader\n", smp_processor_id());
if (m->status & MCI_STATUS_PCC || m->status & MCI_STATUS_OVER)
return MCE_PANIC_SEVERITY;
if (m->status & MCI_STATUS_UC)
return MCE_UC_SEVERITY;
return MCE_KEEP_SEVERITY;
}
int (*mce_severity) (struct mce *m, int tolerant, char **msg, bool
is_excp) =
mce_severity_default;
How much of grading should '_default' do if at all?
Thanks,
-Aravind.
next prev parent reply other threads:[~2015-03-20 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 17:16 [PATCH] x86, mce, severities: Add AMD severities function Aravind Gopalakrishnan
2015-03-17 7:42 ` Ingo Molnar
2015-03-17 9:04 ` Borislav Petkov
2015-03-17 10:11 ` Ingo Molnar
2015-03-17 10:20 ` Borislav Petkov
2015-03-17 18:41 ` Aravind Gopalakrishnan
2015-03-17 18:44 ` Borislav Petkov
2015-03-19 0:01 ` Luck, Tony
2015-03-19 9:29 ` Borislav Petkov
2015-03-19 14:41 ` Aravind Gopalakrishnan
2015-03-19 15:53 ` Borislav Petkov
2015-03-19 16:20 ` Aravind Gopalakrishnan
2015-03-19 17:15 ` Luck, Tony
2015-03-20 15:59 ` Aravind Gopalakrishnan [this message]
2015-03-20 16:03 ` Borislav Petkov
2015-03-20 17:49 ` Luck, Tony
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=550C43E5.4090302@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=slaoub@gmail.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).