linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@intel.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Borislav Petkov <bp@amd64.org>,
	Chen Gong <gong.chen@linux.intel.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: [PATCH 0/2] Add machine check recovery for instruction fetch
Date: Thu, 10 May 2012 11:33:16 -0700	[thread overview]
Message-ID: <cover.1336674796.git.tony.luck@intel.com> (raw)

Part 1 fixes an oversight in the existing code that didn't show
up while I was testing the data recovery case (because I never tried
injecting an error into a clean LRU data page ... only to dirty pages
where "memory_failure()" says we have to SIGBUS the process).

Part simply adds the right entries to the severity table so that we
will recognise instruction fetch faults.

Tony Luck (2):
  x86/mce: Only restart instruction after machine check recovery if it
    is safe
  x86/mce: Add instruction recovery signatures to mce-severity table

 arch/x86/kernel/cpu/mcheck/mce-severity.c |   10 ++++++++++
 arch/x86/kernel/cpu/mcheck/mce.c          |    9 ++++++---
 2 files changed, 16 insertions(+), 3 deletions(-)

-- 
1.7.9.rc2.1.g69204


             reply	other threads:[~2012-05-10 18:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 18:33 Tony Luck [this message]
2012-05-10 18:01 ` [PATCH 1/2] x86/mce: Only restart instruction after machine check recovery if it is safe Tony Luck
2012-05-11  7:19   ` Chen Gong
2012-05-11 16:23     ` Luck, Tony
2012-05-13  9:59   ` Borislav Petkov
2012-05-14 16:16     ` Luck, Tony
2012-05-14 17:17       ` Borislav Petkov
2012-05-14 18:02         ` Tony Luck
2012-05-14 21:55           ` Borislav Petkov
2012-05-10 18:12 ` [PATCH 2/2] x86/mce: Add instruction recovery signatures to mce-severity table Tony Luck
2012-05-11  7:40   ` Chen Gong
2012-05-11 17:42     ` Luck, Tony
2012-05-13 10:05       ` Borislav Petkov
2012-05-14 16:28         ` Luck, Tony
2012-05-14 17:23           ` Borislav Petkov

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=cover.1336674796.git.tony.luck@intel.com \
    --to=tony.luck@intel.com \
    --cc=bp@amd64.org \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).