public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Nikolay Borisov <nik.borisov@suse.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>,
	"Tony Luck" <tony.luck@intel.com>,
	Yazen Ghannam <yazen.ghannam@amd.com>,
	Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
	Avadhut Naik <avadhut.naik@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: 答复: 答复: [外部邮件] Re: [PATCH] x86/mce: Fix timer interval adjustment after logging a MCE event
Date: Mon, 12 Jan 2026 10:24:11 +0000	[thread overview]
Message-ID: <268e2f0512db435685af987a2ba6893c@baidu.com> (raw)
In-Reply-To: <20260112095118.GAaWTEFkUFHMlu0W-A@fat_crate.local>

> On Mon, Jan 12, 2026 at 09:36:21AM +0000, Li,Rongqing wrote:
> > Ok, I will add more explanation, and rename mce_notify_irq() as
> > mce_notify_user();
> 
> No, first you should explain what you're fixing here and why.
> 
> --
> Regards/Gruss,
>     Boris.
> 

How about modifying the changelog as follows


    x86/mce: Fix timer interval adjustment after logging a MCE event

    Since commit 011d82611172 ("RAS: Add a Corrected Errors Collector"),
    mce_timer_fn() has incorrectly determined whether to adjust the
    timer interval. The issue arises because mce_notify_irq() now always
    returns false when called from the timer path, since the polling code
    never sets bit 0 of mce_need_notify. This prevents proper adjustment of
    the timer interval based on whether MCE events were logged.

    The mce_notify_irq() is called from two contexts:
    1. Early notifier block - correctly sets mce_need_notify
    2. Timer function - never sets mce_need_notify, making it a noop
       (though logged errors are still processed through mce_log()->
        x86_mce_decoder_chain -> early notifier).

    Fix this by modifying machine_check_poll() to return a boolean indicating
    whether any MCE was logged, and updating mc_poll_banks() and related
    functions to propagate this return value. Then, mce_timer_fn() can use
    this direct return value instead of relying on mce_notify_irq() for
    timer interval decisions.

    This ensures the timer interval is correctly reduced when MCE events are
    logged and increased when no events occur.

    Fixes: 011d82611172 ("RAS: Add a Corrected Errors Collector")
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2026-01-12 10:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  8:27 [PATCH] x86/mce: Fix timer interval adjustment after logging a MCE event lirongqing
2026-01-12  8:56 ` Nikolay Borisov
2026-01-12  9:36   ` 答复: [外部邮件] " Li,Rongqing
2026-01-12  9:51     ` Borislav Petkov
2026-01-12 10:24       ` Li,Rongqing [this message]
2026-01-13  9:51         ` 答复: " Borislav Petkov
     [not found]           ` <39cfb093256f4da78fe0bc9e814ce5d0@baidu.com>
2026-01-13 12:48             ` 答复: " Borislav Petkov
2026-01-13 18:53               ` Luck, Tony
2026-01-13 18:55                 ` Nikolay Borisov
2026-01-13 19:13                   ` Borislav Petkov
2026-01-13 19:25                     ` Nikolay Borisov
2026-01-13 19:33                       ` Borislav Petkov
2026-01-13 19:37                         ` Nikolay Borisov
2026-01-13 19:44                           ` Borislav Petkov
2026-01-13 19:51                             ` Nikolay Borisov
2026-01-13 20:33                               ` Borislav Petkov
2026-01-13 19:10                 ` Borislav Petkov
2026-01-13 19:31                 ` Nikolay Borisov
2026-01-13 20:30                 ` Thomas Gleixner
2026-01-13 20:56                 ` Borislav Petkov
2026-01-13 21:05                   ` Luck, Tony
2026-01-13 21:31                     ` Borislav Petkov
2026-01-13 22:41                       ` Borislav Petkov
2026-01-14  0:30                         ` Luck, Tony
2026-01-14 13:50                           ` Borislav Petkov
2026-01-14 14:48                             ` Borislav Petkov
2026-02-02 15:18                               ` Borislav Petkov
2026-02-02 23:49                                 ` 答复: [外部邮件] " Li,Rongqing
2026-02-06 22:03                                   ` Borislav Petkov
2026-02-07 11:51                             ` Borislav Petkov
2026-02-09 17:37                               ` Luck, Tony
2026-02-10 15:01                                 ` Borislav Petkov
2026-03-06  7:37                                   ` 答复: [外部邮件] " Li,Rongqing(ACG CCN)
2026-03-06 14:00                                     ` Borislav Petkov
2026-03-06 14:38                                       ` 答复: " Li,Rongqing(ACG CCN)
2026-03-06 15:29                                         ` Borislav Petkov
2026-03-07  1:18                                           ` 答复: " Li,Rongqing(ACG CCN)
2026-03-16 13:44                                             ` Borislav Petkov
2026-01-14  6:17                         ` Nikolay Borisov
2026-01-14 13:52                           ` 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=268e2f0512db435685af987a2ba6893c@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=avadhut.naik@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@amd.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