From: Ashok Raj <ashok.raj@intel.com>
To: linux-kernel@vger.kernel.org
Cc: Ashok Raj <ashok.raj@intel.com>,
linux-edac@vger.kernel.org, Boris Petkov <bp@suse.de>,
Tony Luck <tony.luck@intel.com>
Subject: [Patch V2 0/3] x86, mce: Local Machine Check Exception (LMCE)
Date: Tue, 2 Jun 2015 10:49:51 -0700 [thread overview]
Message-ID: <1433267394-10943-1-git-send-email-ashok.raj@intel.com> (raw)
Hi Boris
Thanks for the feedback on V1. Almost all of your recommendations are
included in this update.
I haven't got a chance to test on qemu yet, but this patch fixes access to
MSR per your recommandation, so should be fine. I'm in process of making
similar changes to kvm/Qemu that i will send once I have learned to build
test it :-).
Historically machine checks on Intel X86 processors have been broadcast to all
logical processors in the system. Upcoming CPUs will support an opt-in
mechanism to request some machine checks delivered to a single logical
processor experiencing the fault.
For more details see Vol3, Chapter 15, Machine Check Architecture.
Modified to incorporate feedback from Boris on V1 patches.
Ashok Raj (3):
x86, mce: Add LMCE definitions.
x86, mce: Add infrastructure required to support LMCE
x86, mce: Handling LMCE events
Documentation/x86/x86_64/boot-options.txt | 3 ++
arch/x86/include/asm/mce.h | 10 ++++++
arch/x86/include/uapi/asm/msr-index.h | 2 ++
arch/x86/kernel/cpu/mcheck/mce.c | 35 ++++++++++++++----
arch/x86/kernel/cpu/mcheck/mce_intel.c | 60 +++++++++++++++++++++++++++++++
5 files changed, 104 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2015-06-02 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 17:49 Ashok Raj [this message]
2015-06-02 17:49 ` [Patch V2 1/3] x86, mce: Add LMCE definitions Ashok Raj
2015-06-02 17:49 ` [Patch V2 2/3] x86, mce: Add infrastructure required to support LMCE Ashok Raj
2015-06-03 10:42 ` Borislav Petkov
2015-06-02 17:49 ` [Patch V2 3/3] x86, mce: Handling LMCE events Ashok Raj
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=1433267394-10943-1-git-send-email-ashok.raj@intel.com \
--to=ashok.raj@intel.com \
--cc=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®