public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	Tony Luck <tony.luck@intel.com>
Subject: Re: [Patch V1] x86, mce: Ensure offline CPU's don't participate in mce rendezvous process.
Date: Sat, 5 Dec 2015 00:06:54 +0100	[thread overview]
Message-ID: <20151204230654.GC21529@pd.tnic> (raw)
In-Reply-To: <20151204235725.GA13057@otc-brkl-03.jf.intel.com>

On Fri, Dec 04, 2015 at 06:57:31PM -0500, Ashok Raj wrote:
> Linux has logical cpu offline capability. That can be triggered by:
> 
> # echo 0 > /sys/devices/system/cpu/cpuX/online
> 
> In Intel Architecture, MCE's are broadcasted to all CPUs in the system.
> 
> This includes the CPUs marked offline by Linux. Unless the CPU's were removed
> via an ACPI notification, in which case the cpu's are removed from the
> cpu_present_map.
> 
> This patch ensures offline CPU's don't participate in MCE rendezvous, but
> simply perform clearing some status bits to ensure a second MCE wont cause
> automatic shutdown.
> 
> Without the patch, mce_start will increment mce_callin, but mce_start would
> only wait for all online_cpus. So offline cpu's should avoid participating
> in the rendezvous process.
> 
> Reviewed-by: Tony Luck <tony.luck@intel.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> ---
>  arch/x86/kernel/cpu/mcheck/mce.c | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
> index c5b0d56..72ea044 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> @@ -998,7 +998,20 @@ void do_machine_check(struct pt_regs *regs, long error_code)
>  	u64 recover_paddr = ~0ull;
>  	int flags = MF_ACTION_REQUIRED;
>  	int lmce = 0;
> +	unsigned int cpu = smp_processor_id();
>  
> +	/*
> +	 * if this cpu is offline, just bail out.
> +	 */
> +	if (cpu_is_offline(cpu)) {
> +		u64 mcgstatus;
> +
> +		mcgstatus = mce_rdmsrl(MSR_IA32_MCG_STATUS);
> +		if (mcgstatus & MCG_STATUS_RIPV) {
> +			mce_wrmsrl(MSR_IA32_MCG_STATUS, 0);
> +			return;
> +		}
> +	}
>  	ist_enter(regs);
>  
>  	this_cpu_inc(mce_exception_count);
> @@ -1142,8 +1155,8 @@ void do_machine_check(struct pt_regs *regs, long error_code)
>  
>  	if (worst > 0)
>  		mce_report_event(regs);
> -	mce_wrmsrl(MSR_IA32_MCG_STATUS, 0);
>  out:
> +	mce_wrmsrl(MSR_IA32_MCG_STATUS, 0);
>  	sync_core();
>  
>  	if (recover_paddr == ~0ull)
> -- 

With that hunk here you want to clear MSR_IA32_MCG_STATUS in the
!cfg->banks case, right?

If so, this should be a separate patch. Also, CC: stable with an
explanation why.

Thanks.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

  reply	other threads:[~2015-12-04 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 23:57 [Patch V1] x86, mce: Ensure offline CPU's don't participate in mce rendezvous process Ashok Raj
2015-12-04 23:06 ` Borislav Petkov [this message]
2015-12-04 23:11   ` Luck, Tony
2015-12-04 23:15     ` 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=20151204230654.GC21529@pd.tnic \
    --to=bp@suse.de \
    --cc=ashok.raj@intel.com \
    --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