All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-edac@kernel.org
Subject: Re: [GIT PULL] RAS update for 3.20 (one more thing)
Date: Mon, 9 Feb 2015 12:01:49 +0100	[thread overview]
Message-ID: <20150209110149.GC4051@pd.tnic> (raw)
In-Reply-To: <20150209101316.GB5461@gmail.com>

On Mon, Feb 09, 2015 at 11:13:16AM +0100, Ingo Molnar wrote:
> This kind of vendor specific hard coding is really ugly:
> 
>         if (c->x86_vendor == X86_VENDOR_AMD && ret == NOTIFY_STOP)
>                 return;

Yeah, I raised the same concern but we already have a bunch of vendor
checks in mce.c anyway so one more shouldn't hurt.

> Instead we should fix the Intel side to do a proper decode 
> as well - by the time mcelog is running it might be too 
> late, attempting an intelligent printk is way better...
> 
> So what would we need to make the Intel side just as good 
> as the AMD side?

The only thing that needs to be done is actually code it, methinks.
Once that's done, we would finally carry ready and decoded information
through a tracepoint to userspace instead of the /dev/mcelog thing.

I'm afraid this won't happen quickly though so we probably would need
this fix for the interim while we're working on the decoding.

Both sides (AMD/Intel) would need to be taught to funnel the decoded
strings through a tracepoint - something which we've talked about in the
past but keeps getting pushed down the TODO list. :-\

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2015-02-09 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 17:41 [GIT PULL] RAS update for 3.20 (one more thing) Luck, Tony
2015-02-09  7:53 ` Ingo Molnar
2015-02-09 10:13 ` Ingo Molnar
2015-02-09 11:01   ` Borislav Petkov [this message]
2015-02-09 18:00     ` [PATCHv3] x86/mce: Fix regression. All error records should report via /dev/mcelog Tony Luck
2015-02-11 18:11       ` Tony Luck

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=20150209110149.GC4051@pd.tnic \
    --to=bp@suse.de \
    --cc=linux-edac@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 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.