Linux EDAC development
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Zhaolong Zhang <zhangzl2013@126.com>, Tony Luck <tony.luck@intel.com>
Cc: x86@kernel.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mce: correct cpu_missing reporting in mce_timed_out
Date: Thu, 4 Nov 2021 10:13:14 +0100	[thread overview]
Message-ID: <YYOkKm8UmmIxSdXF@zn.tnic> (raw)
In-Reply-To: <20211104074431.1091525-1-zhangzl2013@126.com>

On Thu, Nov 04, 2021 at 03:44:31PM +0800, Zhaolong Zhang wrote:
> set cpu_missing before mce_panic() so that it prints correct msg.
> 
> Signed-off-by: Zhaolong Zhang <zhangzl2013@126.com>
> ---
>  arch/x86/kernel/cpu/mce/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> index 50a3e455cded..ccefe131ab55 100644
> --- a/arch/x86/kernel/cpu/mce/core.c
> +++ b/arch/x86/kernel/cpu/mce/core.c
> @@ -903,13 +903,13 @@ static int mce_timed_out(u64 *t, const char *msg)
>  	if (!mca_cfg.monarch_timeout)
>  		goto out;
>  	if ((s64)*t < SPINUNIT) {
> +		cpu_missing = 1;
>  		if (mca_cfg.tolerant <= 1) {
>  			if (cpumask_and(&mce_missing_cpus, cpu_online_mask, &mce_missing_cpus))
>  				pr_emerg("CPUs not responding to MCE broadcast (may include false positives): %*pbl\n",
>  					 cpumask_pr_args(&mce_missing_cpus));
>  			mce_panic(msg, NULL, NULL);
>  		}
> -		cpu_missing = 1;
>  		return 1;
>  	}
>  	*t -= SPINUNIT;
> -- 

Frankly, we might just as well kill that cpu_missing thing because we
already say that some CPUs are not responding.

And that "Some CPUs didn't answer in synchronization" is not really
telling me a whole lot.

Tony, do you see any real need to keep it?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-11-04  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  7:44 [PATCH] x86/mce: correct cpu_missing reporting in mce_timed_out Zhaolong Zhang
2021-11-04  9:13 ` Borislav Petkov [this message]
2021-11-04 15:47   ` Luck, Tony
2021-11-04 18:02     ` Borislav Petkov
2021-11-05  2:19       ` Zhaolong Zhang
2021-11-08  8:28         ` [PATCH] x86/mce: drop cpu_missing since we have more capable mce_missing_cpus Zhaolong Zhang
2021-11-08  9:31           ` Borislav Petkov
2021-11-08 10:13             ` Zhaolong Zhang
2021-11-08 10:31               ` Borislav Petkov
2021-11-08 12:47                 ` Zhaolong Zhang
2021-11-09  8:31                   ` Zhaolong Zhang
2021-11-09  8:35                     ` [PATCH] x86/mce: Get rid of cpu_missing Zhaolong Zhang
2021-11-09  9:15                       ` Borislav Petkov
2021-11-09 14:19                         ` Zhaolong Zhang
2021-11-09  9:07                     ` [PATCH] x86/mce: drop cpu_missing since we have more capable mce_missing_cpus Borislav Petkov
2021-11-09 16:06                       ` Luck, Tony
2021-11-09 19:48                         ` Borislav Petkov
2021-11-09 19:50                           ` Luck, Tony
2021-11-09 20:21                             ` Borislav Petkov
2021-11-09 20:44                               ` Luck, Tony
2021-11-09 21:30                                 ` Borislav Petkov
2021-12-20 20:43                                   ` [PATCH] x86/mce: Remove the tolerance level control 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=YYOkKm8UmmIxSdXF@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=zhangzl2013@126.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