All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>,
	Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
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 17:49:57 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A25A94@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <20150320160337.GE17058@pd.tnic>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 871 bytes --]

>> 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?
>
>I think that should be
>
>	default:
>		WARN_ONCE("WTF?!");
>		break;

mcheck_init() is called unconditionally from setup_arch().  So if anyone is
still using a Cyrix, Transmeta or other non-Intel, non-Amd processor we'd trip this WARN_ON.

I think you can have a default severity function that just does:

	return MCE_PANIC_SEVERITY;

just to avoid the unpleasant thought that we might jump through a NULL pointer
if we did somehow end up in do_machine_check() on another vendors cpu.

-Tony
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

      reply	other threads:[~2015-03-20 17:50 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
2015-03-20 16:03                     ` Borislav Petkov
2015-03-20 17:49                       ` 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=3908561D78D1C84285E8C5FCA982C28F32A25A94@ORSMSX114.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=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=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 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.