From: Borislav Petkov <bp@alien8.de>
To: Rik van Riel <riel@surriel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-team@meta.com" <kernel-team@meta.com>,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] x86/mce: Restore rate limit on MCE logged message
Date: Mon, 9 Nov 2026 13:49:00 -0800 [thread overview]
Message-ID: <20261109214900.GEavI_zEdfTeiCFKLg@fat_crate.local> (raw)
In-Reply-To: <a799adc77dc325f5e3cd9f806dae684f198efd38.camel@surriel.com>
On Mon, Nov 09, 2026 at 04:29:32PM -0500, Rik van Riel wrote:
> I do not know how exactly memory errors are getting
> collected. There are some tools that watch netcons,
> some that collect data on the host, and some that
> grab data off the BMC. I have no idea which of
> those paths the memory error collection uses.
It probably doesn't matter for the problem at hand - I guess we should
ratelimit that printk after all...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2026-11-09 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 19:37 Rik van Riel
2026-11-08 20:28 ` Borislav Petkov
2026-11-09 17:54 ` Luck, Tony
2026-11-09 19:52 ` Borislav Petkov
2026-11-09 20:12 ` Rik van Riel
2026-11-09 21:23 ` Borislav Petkov
2026-11-09 21:29 ` Rik van Riel
2026-11-09 21:49 ` Borislav Petkov [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=20261109214900.GEavI_zEdfTeiCFKLg@fat_crate.local \
--to=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=qiuxu.zhuo@intel.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®