From: Sohil Mehta <sohil.mehta@intel.com>
To: Breno Leitao <leitao@debian.org>, Tony Luck <tony.luck@intel.com>,
Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Qiuxu Zhuo <qzhuo@nvidia.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@surriel.com>, <kernel-team@meta.com>
Subject: Re: [PATCH v3 2/2] x86/mce: Rate-limit the CMCI storm transition notices
Date: Fri, 13 Nov 2026 13:20:03 -0800 [thread overview]
Message-ID: <3650daff-48cc-48dc-a2cb-cdfbe91ef3df@intel.com> (raw)
In-Reply-To: <20261113-mci_ratelimit-v3-2-ada38c5a6c88@debian.org>
On 11/13/2026 4:49 AM, Breno Leitao wrote:
> mce_track_storm() prints a line every time a bank enters storm mode and
> another every time it leaves. Neither is bounded, so the log volume
> follows whatever rate the bank flaps at.
>
> One host in our fleet logged 9970726 "CMCI storm detected" and 9970734
> "CMCI storm subsided" lines for a single bank over four days, which is
> a bit excessive for all monitoring purposes.
>
> Put both transitions behind one ratelimit.
>
> Acked-by: Tony Luck <tony.luck@intel.com>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
A minor nit below.
> arch/x86/kernel/cpu/mce/threshold.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mce/threshold.c b/arch/x86/kernel/cpu/mce/threshold.c
> index 6c370d5af5bd23..8591715ce24306 100644
> --- a/arch/x86/kernel/cpu/mce/threshold.c
> +++ b/arch/x86/kernel/cpu/mce/threshold.c
> @@ -4,6 +4,7 @@
> */
> #include <linux/interrupt.h>
> #include <linux/kernel.h>
> +#include <linux/ratelimit.h>
>
> #include <asm/irq_vectors.h>
> #include <asm/traps.h>
> @@ -111,6 +112,13 @@ void cmci_storm_end(unsigned int bank)
> mce_timer_kick(false);
> }
>
> +/*
> + * Shared by both transitions so that a bank flapping between them cannot
> + * outrun the console.
> + */
> +static DEFINE_RATELIMIT_STATE(storm_rs, DEFAULT_RATELIMIT_INTERVAL,
> + DEFAULT_RATELIMIT_BURST);
> +
Should this be defined as a function local similar to patch 1?
> void mce_track_storm(struct mce *mce)
> {
> struct mca_storm_desc *storm = this_cpu_ptr(&storm_desc);
> @@ -150,13 +158,17 @@ void mce_track_storm(struct mce *mce)
> if (storm->banks[mce->bank].in_storm_mode) {
> if (history & GENMASK_ULL(STORM_END_POLL_THRESHOLD, 0))
> return;
> - printk_deferred(KERN_NOTICE "CPU%d BANK%d CMCI storm subsided\n", smp_processor_id(), mce->bank);
> + if (__ratelimit(&storm_rs))
> + printk_deferred(KERN_NOTICE "CPU%d BANK%d CMCI storm subsided\n",
> + smp_processor_id(), mce->bank);
> mce_handle_storm(mce->bank, false);
> cmci_storm_end(mce->bank);
> } else {
> if (hweight64(history) < STORM_BEGIN_THRESHOLD)
> return;
> - printk_deferred(KERN_NOTICE "CPU%d BANK%d CMCI storm detected\n", smp_processor_id(), mce->bank);
> + if (__ratelimit(&storm_rs))
> + printk_deferred(KERN_NOTICE "CPU%d BANK%d CMCI storm detected\n",
> + smp_processor_id(), mce->bank);
> mce_handle_storm(mce->bank, true);
> cmci_storm_begin(mce->bank);
> }
>
prev parent reply other threads:[~2026-11-13 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 12:49 [PATCH v3 0/2] x86/mce: Rate-limit messages from corrected error floods Breno Leitao
2026-11-13 12:49 ` [PATCH v3 1/2] x86/mce: Restore rate limit on MCE logged message Breno Leitao
2026-11-13 21:15 ` Sohil Mehta
2026-11-13 12:49 ` [PATCH v3 2/2] x86/mce: Rate-limit the CMCI storm transition notices Breno Leitao
2026-11-13 15:38 ` Qiuxu (Leo) Zhuo
2026-11-13 21:20 ` Sohil Mehta [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=3650daff-48cc-48dc-a2cb-cdfbe91ef3df@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qzhuo@nvidia.com \
--cc=riel@surriel.com \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®