From: Borislav Petkov <bp@alien8.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
Borislav Petkov <bp@suse.de>, Tony Luck <tony.luck@intel.com>
Subject: Re: [Patch V1 3/3] x86, mce: Handling LMCE events
Date: Fri, 29 May 2015 19:36:23 +0200 [thread overview]
Message-ID: <20150529173623.GN31435@pd.tnic> (raw)
In-Reply-To: <1432916882-1304-4-git-send-email-ashok.raj@intel.com>
On Fri, May 29, 2015 at 09:28:02AM -0700, Ashok Raj wrote:
> This patch has handling changes to do_machine_check() to process MCE
> signaled as local MCE. Typically only recoverable errors (SRAR) type
> error will be Signaled as LMCE. But architecture does not restrict to
> only those errors.
>
> When errors are signaled as LMCE, there is no need for the MCE handler to
> perform rendezvous with other logical processors unlike earlier processors
> that would broadcast machine check errors.
>
> See http://www.intel.com/sdm Volume 3, Chapter 15 for more information
> on MSR's and documentation on Local MCE.
>
> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> ---
> arch/x86/kernel/cpu/mcheck/mce.c | 25 ++++++++++++++++++++++---
> arch/x86/kernel/cpu/mcheck/mce_intel.c | 1 +
> 2 files changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
> index d10aada..c130391 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> @@ -1047,6 +1047,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)
> char *msg = "Unknown";
> u64 recover_paddr = ~0ull;
> int flags = MF_ACTION_REQUIRED;
> + int lmce = 0;
>
> prev_state = ist_enter(regs);
>
> @@ -1074,11 +1075,19 @@ void do_machine_check(struct pt_regs *regs, long error_code)
> kill_it = 1;
>
> /*
> + * Check if this MCE is signaled to only this logical processor
> + */
> + if (m.mcgstatus & MCG_STATUS_LMCES)
> + lmce = 1;
else
/*
* Go through ...
* ...
*/
order = mce_start(&no_way_out);
> + /*
> * Go through all the banks in exclusion of the other CPUs.
> * This way we don't report duplicated events on shared banks
> * because the first one to see it will clear it.
> + * If this is a Local MCE, then no need to perform rendezvous.
> */
> - order = mce_start(&no_way_out);
> + if (!lmce)
> + order = mce_start(&no_way_out);
> +
> for (i = 0; i < cfg->banks; i++) {
> __clear_bit(i, toclear);
> if (!test_bit(i, valid_banks))
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-05-29 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 16:27 [Patch V1 0/3] x86 Local Machine Check Exception (LMCE) Ashok Raj
2015-05-29 16:28 ` [Patch V1 1/3] x86, mce: Add LMCE definitions Ashok Raj
2015-05-29 16:28 ` [Patch V1 2/3] x86, mce: Add infrastructure required to support LMCE Ashok Raj
2015-05-29 17:35 ` Borislav Petkov
2015-05-29 17:44 ` Borislav Petkov
2015-06-01 17:09 ` Raj, Ashok
2015-06-01 18:48 ` Raj, Ashok
2015-06-01 19:37 ` Borislav Petkov
2015-05-29 16:28 ` [Patch V1 3/3] x86, mce: Handling LMCE events Ashok Raj
2015-05-29 17:36 ` Borislav Petkov [this message]
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=20150529173623.GN31435@pd.tnic \
--to=bp@alien8.de \
--cc=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