From: Breno Leitao <leitao@debian.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: 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>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 2/2] x86/mce: Add mce=panic_on_ce_count to panic on a corrected error flood
Date: Tue, 25 Aug 2026 06:55:15 -0700 [thread overview]
Message-ID: <ao2eT0TWS9EaA28N@gmail.com> (raw)
In-Reply-To: <aoynhOsTCcapwRbl@agluck-desk3>
On Mon, Aug 24, 2026 at 01:20:20PM -0700, Luck, Tony wrote:
> > > One question while I am here: is the approach itself something you are
> > > willing to take, or, just a just send patch [1/2]?
> >
> > Boris is the maintainer here. So he has the final decision. My
> > opinion is that this is a bit niche for the kernel. Maybe this
> > could be handled by some user agent (mcelog? rasdaemon?) to
> > raise awareness to system operators about high rates of corrected
> > errors.
>
> I chatted with someone internally. They'd be very interested in being
> able to see these running counts via some /sys files.
>
> Perhaps your use case would be better for that too? Rather than:
>
> "Everything is fine"
Sounds good, I will restructure v2 that way: export the running counts
first, and add the panic on top as a separate patch.
The count is already kept per CPU and per bank in struct storm_bank, so
the natural fit is one read-only file per bank, next to the existing
bank<N> knobs:
/sys/devices/system/machinecheck/machinecheckX/ce_count<N>
Is this the right approach?
Thanks
--breno
next prev parent reply other threads:[~2026-08-25 13:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 10:24 [PATCH 0/2] x86/mce: Rate-limit storm notices and add a corrected error ceiling Breno Leitao
2026-08-21 10:24 ` [PATCH 1/2] x86/mce: Rate-limit the CMCI storm transition notices Breno Leitao
2026-08-21 16:18 ` Luck, Tony
2026-08-21 16:35 ` Breno Leitao
2026-08-27 9:49 ` Breno Leitao
2026-08-21 10:24 ` [PATCH 2/2] x86/mce: Add mce=panic_on_ce_count to panic on a corrected error flood Breno Leitao
2026-08-21 16:50 ` Luck, Tony
2026-08-24 8:29 ` Breno Leitao
2026-08-24 16:31 ` Luck, Tony
2026-08-24 20:20 ` Luck, Tony
2026-08-25 13:55 ` Breno Leitao [this message]
2026-08-25 15:27 ` Luck, Tony
2026-08-25 16:16 ` Borislav Petkov
2026-08-25 16:26 ` Luck, Tony
2026-08-25 19:15 ` Borislav Petkov
2026-08-25 20:01 ` Luck, Tony
2026-08-25 22:52 ` Borislav Petkov
2026-08-26 13:22 ` Breno Leitao
2026-08-26 16:09 ` Borislav Petkov
2026-08-26 17:32 ` Luck, Tony
2026-08-31 4:57 ` Borislav Petkov
2026-08-27 9:47 ` Breno Leitao
2026-08-27 14:28 ` Borislav Petkov
2026-08-24 20:47 ` Luck, Tony
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=ao2eT0TWS9EaA28N@gmail.com \
--to=leitao@debian.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.