All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@amd64.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PULL] MCE recovery changes
Date: Thu, 26 Jan 2012 11:46:46 +0100	[thread overview]
Message-ID: <20120126104646.GF3853@elte.hu> (raw)
In-Reply-To: <4f1f396019579c94fb@agluck-desktop.sc.intel.com>


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

> Ingo,
> 
> Time to move these from "ras" tree to "tip" so they will be nicely
> seasoned for the 3.4 merge window.
> 
> I tried to follow the instructions in
>  http://git-blame.blogspot.com/2012/01/using-signed-tag-in-pull-requests.html
> to use the fancy new signed tag scheme. If something is wrong here, then it
> is most likely that I typoed (or thinkoed) while following them.

It worked perfectly.

> 
> -Tony
> 
> The following changes since commit dc47ce90c3a822cd7c9e9339fe4d5f61dcb26b50:
> 
>   Linux 3.2-rc5 (2011-12-09 15:09:32 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git mce-recovery-for-tip
> 
> for you to fetch changes up to 5f7b88d51e89771f64c15903b96b5933dd0bc6d8:
> 
>   x86/mce: Recognise machine check bank signature for data path error (2012-01-03 12:07:07 -0800)
> 
> ----------------------------------------------------------------
> MCE recovery (data path only)
> 
> ----------------------------------------------------------------
> Tony Luck (6):
>       HWPOISON: Clean up memory_failure() vs. __memory_failure()
>       HWPOISON: Add code to handle "action required" errors.
>       x86/mce: Create helper function to save addr/misc when needed
>       x86/mce: Add mechanism to safely save information in MCE handler
>       x86/mce: Handle "action required" errors
>       x86/mce: Recognise machine check bank signature for data path error
> 
>  arch/x86/kernel/cpu/mcheck/mce-severity.c |   16 +++-
>  arch/x86/kernel/cpu/mcheck/mce.c          |  179 ++++++++++++++++++++---------
>  drivers/base/memory.c                     |    2 +-
>  include/linux/mm.h                        |    4 +-
>  mm/hwpoison-inject.c                      |    4 +-
>  mm/madvise.c                              |    2 +-
>  mm/memory-failure.c                       |   96 ++++++++--------
>  7 files changed, 197 insertions(+), 106 deletions(-)

Pulled, thanks!

One thing i noticed was the magic constant 0x134:

+               SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR|MCI_ADDR|MCACOD, MCI_UC_SAR|MCI_ADDR|0x0134),

don't we want that defined a bit more clearly?

Thanks,

	Ingo

  reply	other threads:[~2012-01-26 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 23:06 [GIT PULL] MCE recovery changes Luck, Tony
2012-01-26 10:46 ` Ingo Molnar [this message]
2012-01-26 17:29   ` Tony Luck
2012-01-26 18:28     ` Ingo Molnar
2012-01-27  0:02       ` [PATCH] x86/mce: Replace hard coded hex constants with symbolic defines Tony Luck
2012-01-27 10:49         ` Ingo Molnar

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=20120126104646.GF3853@elte.hu \
    --to=mingo@elte.hu \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.