From: Ingo Molnar <mingo@elte.hu>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH for tip/mce3] x86, mce: Add options for corrected errors
Date: Thu, 11 Jun 2009 11:47:06 +0200 [thread overview]
Message-ID: <20090611094706.GB12703@elte.hu> (raw)
In-Reply-To: <4A30ACDF.5030408@jp.fujitsu.com>
* Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> wrote:
> [ Repost, rebased on tip/x86/mce3]
>
> This patch introduces three boot options (no_cmci, dont_log_ce and
> ignore_ce) to control handling for corrected errors.
>
> The "mce=no_cmci" boot option disables cmci feature. Since cmci is
> a new feature so having boot controls to disable it will be a help
> if the hardware is misbehaving.
>
> The "mce=dont_log_ce" boot option disables logging for corrected
> errors. All reported corrected errors will be cleared silently.
> This option will be useful if you never care corrected errors.
>
> The "mce=ignore_ce" boot option disables features for corrected
> errors, i.e. polling timer and cmci. All corrected events are not
> cleared and kept in bank MSRs. Usually this disablement is not
> recommended, however it will be a help if there are some conflict
> with the BIOS or hardware monitoring applications etc., that
> clears corrected events in banks instead of OS.
Applied to tip:x86/mce3, thanks Hidetoshi!
A few sidenote:
Please introduce a sysctl for these too, for those were the flag can
be safely toggled after bootup (most of them look to be such flags).
Admins might want to tweak these options without rebooting the
system.
Even for those flags where a toggle means having to touch MSRs to
deactivate/(reactivate) CMCI we should do the sysctl thing, as
no-reboot configurability is king in this space.
a few random details:
> static int mce_bootlog = -1;
> static int monarch_timeout = -1;
> static int mce_panic_timeout;
> +static int mce_dont_log_ce;
> +int mce_cmci_disabled;
> +int mce_ignore_ce;
> int mce_ser;
All rarely-modified variables should be declared __read_mostly.
> static char trigger[128];
Undocumented magic constant and meaninglessly named global variable,
please clean this up.
Ingo
next prev parent reply other threads:[~2009-06-11 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 7:06 Hidetoshi Seto
2009-06-11 9:47 ` Ingo Molnar [this message]
2009-06-12 0:56 ` Hidetoshi Seto
2009-06-11 9:48 ` [tip:branch?] x86, mce: Add boot " tip-bot for Hidetoshi Seto
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=20090611094706.GB12703@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
/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®