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 19:08:10 +0200
Date: Fri, 27 Apr 2007 19:08:10 +0200 [thread overview]
Message-ID: <20070427170810.GB4574@muc.de> (raw)
In-Reply-To: <cc96a5040704271005p5976dec6nb7f99d6cd099de95@mail.gmail.com>
On Fri, Apr 27, 2007 at 10:05:58AM -0700, Tim Hockin wrote:
> On 27 Apr 2007 19:02:30 +0200, Andi Kleen <ak@muc.de> wrote:
> >On Fri, Apr 27, 2007 at 09:58:14AM -0700, Tim Hockin wrote:
> >> On 27 Apr 2007 11:09:17 +0200, Andi Kleen <ak@muc.de> wrote:
> >> >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?
> >>
> >> Which documentation, specifically? :)
> >
> >Documentation/x86_64/{boot-options.txt,machinecheck}
>
> What needs to be changed in boot-options?
Nothing for your patch sorry. Only in machinecheck
-Andi
next prev parent reply other threads:[~2007-04-27 17:08 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
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 [this message]
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=20070427170810.GB4574@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