public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-edac@kernel.org, Borislav Petkov <bp@suse.de>
Subject: Re: [GIT PULL] RAS update for 3.20 (one more thing)
Date: Mon, 9 Feb 2015 11:13:16 +0100	[thread overview]
Message-ID: <20150209101316.GB5461@gmail.com> (raw)
In-Reply-To: <54cfb6e332538eb6ea@agluck-desk.sc.intel.com>


* Luck, Tony <tony.luck@intel.com> wrote:

> The following changes since commit 26bc420b59a38e4e6685a73345a0def461136dce:
> 
>   Linux 3.19-rc6 (2015-01-25 20:04:41 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/please-pull-fixmcelog
> 
> for you to fetch changes up to 728b6f14abaa7f36a8c6d41c6d6fe0320d32d5e9:
> 
>   x86, mce: Kernel does full decoding for AMD, others still need /dev/mcelog reports (2015-01-30 11:25:46 -0800)
> 
> ----------------------------------------------------------------
> Long standing regression - functions registered on the mce decoder
> chain can declare that they have completely dealt with an event.
> True for AMD (says Boris), since the kernel fully decodes the
> machine check bank information. Not true for Intel processors. Full
> decode is done in user space, so we need to make the log visible
> via /dev/mcelog

So I'm having second thoughts about this:

This kind of vendor specific hard coding is really ugly:

        if (c->x86_vendor == X86_VENDOR_AMD && ret == NOTIFY_STOP)
                return;

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?

I've undone the pull for now.

Thanks,

	Ingo

  parent reply	other threads:[~2015-02-09 10:13 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 [this message]
2015-02-09 11:01   ` Borislav Petkov
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=20150209101316.GB5461@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=linux-edac@kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox