From: Borislav Petkov <bp@alien8.de>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, tony.luck@intel.com
Subject: Re: [PATCH v2 2/3] x86/mce: Move message printing from mce_notify_irq to mce_early_notifier()
Date: Tue, 25 Feb 2025 14:10:00 +0100 [thread overview]
Message-ID: <20250225131000.GKZ73BKIW4SqS4cbbE@fat_crate.local> (raw)
In-Reply-To: <20250210154707.114219-3-nik.borisov@suse.com>
On Mon, Feb 10, 2025 at 05:47:05PM +0200, Nikolay Borisov wrote:
> Informing the user that an MCE has been logged from mce_notify_irq() is
> somewhat misleading because whether the MCE has been logged actually
> depends on whether CONFIG_X86_MCELOG_LEGACY is turned on or not.
That text needs update in light of what we talked about when looking at patch
1...
> Furthermore it was reported that actually having a message triggered
> when an MCE is generated can be helpful in certain scenarios.
That's too vague - needs proper justification.
> Improve the situation by lifting the printing to the generic
> mce_early_notifier() as it's executed always and is independent of any
> compile-time option.
Meh.
> Link: https://lore.kernel.org/all/CY8PR11MB7134D97F82DC001AE009637889E32@CY8PR11MB7134.namprd11.prod.outlook.com/
Ah, there's the justification. I guess...
Just don't put "customers" in the commit message.
> Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
> ---
> arch/x86/kernel/cpu/mce/core.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> index 89625ff79c3b..d55b1903fde6 100644
> --- a/arch/x86/kernel/cpu/mce/core.c
> +++ b/arch/x86/kernel/cpu/mce/core.c
> @@ -591,15 +591,8 @@ EXPORT_SYMBOL_GPL(mce_is_correctable);
> */
> static int mce_notify_irq(void)
> {
> - /* Not more than two messages every minute */
> - static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2);
> -
> if (test_and_clear_bit(0, &mce_need_notify)) {
> mce_work_trigger();
> -
> - if (__ratelimit(&ratelimit))
> - pr_info(HW_ERR "Machine check events logged\n");
> -
> return 1;
> }
>
> @@ -609,6 +602,8 @@ static int mce_notify_irq(void)
> static int mce_early_notifier(struct notifier_block *nb, unsigned long val,
> void *data)
> {
> + /* Not more than two messages every minute */
> + static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2);
> struct mce_hw_err *err = to_mce_hw_err(data);
>
> if (!err)
> @@ -619,6 +614,9 @@ static int mce_early_notifier(struct notifier_block *nb, unsigned long val,
>
> set_bit(0, &mce_need_notify);
>
> + if (__ratelimit(&ratelimit))
> + pr_info(HW_ERR "Machine check event detected\n");
Well, the previous "logged" was correct.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-02-25 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:47 [PATCH v2 0/3] Simpify mce code somewhat Nikolay Borisov
2025-02-10 15:47 ` [PATCH v2 1/3] x86/mce/inject: Remove call to mce_notify_irq() Nikolay Borisov
2025-02-11 7:03 ` Zhuo, Qiuxu
2025-02-11 8:49 ` Nikolay Borisov
2025-02-11 12:37 ` Zhuo, Qiuxu
2025-02-16 16:10 ` Borislav Petkov
2025-02-17 10:01 ` Nikolay Borisov
2025-02-17 11:20 ` Nikolay Borisov
2025-02-17 11:47 ` Borislav Petkov
2025-02-10 15:47 ` [PATCH v2 2/3] x86/mce: Move message printing from mce_notify_irq to mce_early_notifier() Nikolay Borisov
2025-02-11 7:10 ` Zhuo, Qiuxu
2025-02-25 13:10 ` Borislav Petkov [this message]
2025-02-10 15:47 ` [PATCH v2 3/3] x86/mce: Make mce_notify_irq() depend on CONFIG_X86_MCELOG_LEGACY Nikolay Borisov
2025-02-11 7:20 ` Zhuo, Qiuxu
2025-02-11 10:18 ` Nikolay Borisov
2025-02-25 13:12 ` 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=20250225131000.GKZ73BKIW4SqS4cbbE@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--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®