From: Andi Kleen <ak@muc.de>
To: Tim Hockin <thockin@google.com>
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org, akpm@google.com
Subject: Re: [PATCH] x86_64: dynamic MCE poll interval
Date: 27 Apr 2007 11:09:17 +0200
Date: Fri, 27 Apr 2007 11:09:17 +0200 [thread overview]
Message-ID: <20070427090917.GA24922@muc.de> (raw)
In-Reply-To: <cc96a5040704261802v2bcb3a59k9d44da8d615a6779@mail.gmail.com>
On Thu, Apr 26, 2007 at 06:02:52PM -0700, Tim Hockin wrote:
> Description:
> This patch makes the MCE poller adjust the polling interval dynamically.
> If we find an MCE, poll 2x faster (down to 10 ms). When we stop finding
> MCEs, poll 2x slower (up to check_interval seconds). The check_interval
> tunable becomes the max polling interval.
Can you please fix the documentation then?
>
> Result:
> If you start to take a lot of correctable errors (not exceptions), you
> log them faster and more accurately (less chance of overflowing the MCA
> registers). If you don't take a lot of errors, you will see no change.
Makes sense.
AMD RevF can do this using the threshold interrupts too for DIMM errors
too without any delays -- perhaps it would also make sense to configure
this by default that it always triggers on all DIMM errors.
Right now it is just an option in /sys
> @@ -349,17 +349,24 @@ static void mcheck_timer(struct work_str
> * writes.
> */
> if (notify_user && console_logged) {
> + /* if we logged an MCE, reduce the polling interval */
> + next_interval = max(next_interval/2, HZ/100);
> notify_user = 0;
> clear_bit(0, &console_logged);
> printk(KERN_INFO "Machine check events logged\n");
The printk should not happen too often. Can you add some hardcoded
limit there than it doesn't happen more often than every hour or so
(or perhaps use a exponential backoff here too?)
It is only to tell users to check mcelog output.
-Andi
next prev parent reply other threads:[~2007-04-27 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:02 [PATCH] x86_64: dynamic MCE poll interval Tim Hockin
2007-04-27 9:09 ` Andi Kleen [this message]
2007-04-27 16:58 ` Tim Hockin
2007-04-27 17:02 ` Andi Kleen
2007-04-27 17:05 ` Tim Hockin
2007-04-27 17:08 ` Andi Kleen
2007-04-27 18:28 ` Tim Hockin
2007-04-27 19:28 ` Andi Kleen
2007-04-27 20:51 ` Tim Hockin
2007-04-27 21:03 ` Tim Hockin
2007-04-27 21:19 ` Randy Dunlap
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=20070427090917.GA24922@muc.de \
--to=ak@muc.de \
--cc=akpm@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@google.com \
--cc=vojtech@suse.cz \
/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