From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
Borislav Petkov <bp@suse.de>,
Chen Gong <gong.chen@linux.intel.com>
Subject: Re: [PATCHv2] x86, mce: Kernel does full decoding for AMD, others still need /dev/mcelog reports
Date: Fri, 30 Jan 2015 20:13:55 +0100 [thread overview]
Message-ID: <20150130191355.GH1451@pd.tnic> (raw)
In-Reply-To: <3d6a39202cff6415eeb0af7bff58f36ce879a253.1422641617.git.tony.luck@intel.com>
On Fri, Jan 30, 2015 at 10:16:48AM -0800, Tony Luck wrote:
> We should only believe a NOTIFY_STOP on an AMD system. For others
> we need to provide the error record out to a user level decoder
> via /dev/mcelog.
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
> v2: Boris says: "on AMD, mcelog is not needed"
>
> arch/x86/kernel/cpu/mcheck/mce.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
> index d2c611699cd9..ea1bc1a05c07 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> @@ -151,12 +151,13 @@ void mce_log(struct mce *mce)
> {
> unsigned next, entry;
> int ret = 0;
> + struct cpuinfo_x86 *c = &boot_cpu_data;
>
> /* Emit the trace record: */
> trace_mce_record(mce);
>
> ret = atomic_notifier_call_chain(&x86_mce_decoder_chain, 0, mce);
> - if (ret == NOTIFY_STOP)
> + if (c->x86_vendor == X86_VENDOR_AMD && ret == NOTIFY_STOP)
Yeah, ok, we do other vendor checks in mce.c already.
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-01-30 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 17:29 [PATCH] x86, mce: Always fall into mcelog path, regardless of what notifiers returned Tony Luck
2015-01-30 17:38 ` Borislav Petkov
2015-01-30 18:16 ` [PATCHv2] x86, mce: Kernel does full decoding for AMD, others still need /dev/mcelog reports Tony Luck
2015-01-30 19:13 ` Borislav Petkov [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=20150130191355.GH1451@pd.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®