From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"kernel-team@fb.com" <kernel-team@fb.com>
Subject: Re: [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs
Date: Wed, 6 Jan 2021 16:41:48 -0800 [thread overview]
Message-ID: <20210107004148.GJ2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <366fc78e7b8c4474958b289eec31ed25@intel.com>
On Thu, Jan 07, 2021 at 12:26:19AM +0000, Luck, Tony wrote:
> > Please see below for an updated patch.
>
> Yes. That worked:
>
> [ 78.946069] mce: mce_timed_out: MCE holdout CPUs (may include false positives): 24-47,120-143
> [ 78.946151] mce: mce_timed_out: MCE holdout CPUs (may include false positives): 24-47,120-143
> [ 78.946153] Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
>
> I guess that more than one CPU hit the timeout and so your new message was printed twice
> before the panic code took over?
Could well be.
It would be easy to add a flag that allowed only one CPU to print the
message. Does that make sense? (See off-the-cuff probably-broken
delta patch below for one approach.)
> Once again, the whole of socket 1 is MIA rather than just the pair of threads on one of the cores there.
> But that's a useful improvement (eliminating the other three sockets on this system).
>
> Tested-by: Tony Luck <tony.luck@intel.com>
Thank you very much! I will apply this.
Thanx, Paul
------------------------------------------------------------------------
diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
index 7a6e1f3..b46ac56 100644
--- a/arch/x86/kernel/cpu/mce/core.c
+++ b/arch/x86/kernel/cpu/mce/core.c
@@ -882,6 +882,7 @@ static atomic_t mce_callin;
*/
static cpumask_t mce_present_cpus;
static cpumask_t mce_missing_cpus;
+static atomic_t mce_missing_cpus_gate;
/*
* Check if a timeout waiting for other CPUs happened.
@@ -900,7 +901,7 @@ static int mce_timed_out(u64 *t, const char *msg)
if (!mca_cfg.monarch_timeout)
goto out;
if ((s64)*t < SPINUNIT) {
- if (mca_cfg.tolerant <= 1) {
+ if (mca_cfg.tolerant <= 1 && !atomic_xchg(&mce_missing_cpus_gate, 1)) {
if (cpumask_andnot(&mce_missing_cpus, cpu_online_mask, &mce_present_cpus))
pr_info("%s: MCE holdout CPUs (may include false positives): %*pbl\n",
__func__, cpumask_pr_args(&mce_missing_cpus));
@@ -1017,6 +1018,7 @@ static int mce_start(int *no_way_out)
*/
order = atomic_inc_return(&mce_callin);
cpumask_set_cpu(smp_processor_id(), &mce_present_cpus);
+ atomic_set(&mce_missing_cpus_gate, 0);
/*
* Wait for everyone.
@@ -1126,6 +1128,7 @@ static int mce_end(int order)
atomic_set(&global_nwo, 0);
atomic_set(&mce_callin, 0);
cpumask_clear(&mce_present_cpus);
+ atomic_set(&mce_missing_cpus_gate, 0);
barrier();
/*
@@ -2725,6 +2728,7 @@ static void mce_reset(void)
atomic_set(&mce_callin, 0);
atomic_set(&global_nwo, 0);
cpumask_clear(&mce_present_cpus);
+ atomic_set(&mce_missing_cpus_gate, 0);
}
static int fake_panic_get(void *data, u64 *val)
next prev parent reply other threads:[~2021-01-07 0:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 17:41 [PATCH RFC x86/mce] Make mce_timed_out() identify holdout CPUs Paul E. McKenney
2021-01-06 18:32 ` Borislav Petkov
2021-01-06 19:13 ` Paul E. McKenney
2021-01-07 7:07 ` Borislav Petkov
2021-01-07 17:08 ` Paul E. McKenney
2021-01-08 12:31 ` Borislav Petkov
2021-01-08 14:55 ` Paul E. McKenney
2021-01-08 16:57 ` Borislav Petkov
2021-01-06 18:39 ` Luck, Tony
2021-01-06 19:17 ` Paul E. McKenney
2021-01-06 22:49 ` Luck, Tony
2021-01-06 23:23 ` Paul E. McKenney
2021-01-07 0:26 ` Luck, Tony
2021-01-07 0:41 ` Paul E. McKenney [this message]
2021-01-08 17:09 ` [tip: ras/core] x86/mce: " tip-bot2 for Paul E. McKenney
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=20210107004148.GJ2743@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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