From: "Luck, Tony" <tony.luck@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
x86@kernel.org
Subject: [GIT PULL] Couple more changes for x86/ras branch
Date: Thu, 20 Nov 2014 15:07:57 -0800 [thread overview]
Message-ID: <546e744d25585e3421@agluck-desk.sc.intel.com> (raw)
The following changes since commit 8dcf32ea220d87ca517e164de85d336480c9d172:
x86, MCE, AMD: Assign interrupt handler only when bank supports it (2014-11-01 11:28:23 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/please-pull-ucna
for you to fetch changes up to fa92c58694268a7e9f7fa2c6881c1482221c2788:
x86, mce: Support memory error recovery for both UCNA and Deferred error in machine_check_poll (2014-11-19 10:56:51 -0800)
----------------------------------------------------------------
Handle all uncorrected error reports in the same way (soft offline
the page). We used to only do that for SRAO (software recoverable
action optional) machine checks, but it makes sense to also do it
for UCNA (UnCorrected No Action) logs found by CMCI or polling.
----------------------------------------------------------------
Chen Yucong (2):
x86, mce, severity: Extend the the mce_severity mechanism to handle UCNA/DEFERRED error
x86, mce: Support memory error recovery for both UCNA and Deferred error in machine_check_poll
arch/x86/include/asm/mce.h | 4 +++
arch/x86/kernel/cpu/mcheck/mce-internal.h | 4 ++-
arch/x86/kernel/cpu/mcheck/mce-severity.c | 23 ++++++++----
arch/x86/kernel/cpu/mcheck/mce.c | 60 +++++++++++++++++++++++++++----
drivers/edac/mce_amd.h | 3 --
5 files changed, 78 insertions(+), 16 deletions(-)
reply other threads:[~2014-11-20 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=546e744d25585e3421@agluck-desk.sc.intel.com \
--to=tony.luck@intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®