From: Andi Kleen <andi@firstfloor.org>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@linux.intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RESEND][PATCH -tip 2/3] x86, mce: Revert "add mce=nopoll option to disable timer polling"\
Date: Mon, 20 Apr 2009 12:03:23 +0200 [thread overview]
Message-ID: <20090420100323.GW14687@one.firstfloor.org> (raw)
In-Reply-To: <49EC3AB5.5070902@jp.fujitsu.com>
> 1) There is a agent checking/clearing corrected errors
> (such as BIOS) other than OS.
>
> In this case, clearing MSRs by OS is not applicable.
> So ignore_ce is better option here.
Yes, but how do you make sure the option is set when the agent is active?
I think relying on a kernel boot option here is quite fragile.
Also it's something the administrator shouldn't be involved in.
>
> 2) There is no agent checking/clearing corrected errors.
> User just want to suppress logs of corrected errors.
>
> In this case, dont_log_ce would be better option.
> (Or adding filter to mcelog would be another solution)
>
> I don't mind adding three options (no_cmci/ignore_ce/dont_log_ce)
> at once. I'll rework 3/3 of this series to do so.
>
> > Also for your use case really the better way would be to use
> > some way to let the firmware communicate that it doesn't want the OS
> > to log.
>
> Yes. However AFAIK there is no way to do it yet.
We can just define one. We had Linux specific extensions before.
Just needs a new bit somewhere. I think that would give a better
experience for your customers.
There might be something forthcomming that could be usable in fact.
> The original of this repost were posted about three weeks ago (Apr.2)...
>
> I think your patches will go smoothly if my revert patches added before
> them.
The bug fixes should go in 2.6.30. After all that is what the rc stage
is for -- applying bug fixed.
> BTW, could you give me your Acked-by on this 2/3 too?
Not yet sorry.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-20 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 1:19 [RESEND][PATCH -tip 0/3] x86, mce: re-implement options for corrected errors Hidetoshi Seto
2009-04-20 1:26 ` [RESEND][PATCH -tip 1/3] x86, mce: Revert "add mce_threshold option for intel cmci" Hidetoshi Seto
2009-04-20 7:20 ` Andi Kleen
2009-04-20 1:27 ` [RESEND][PATCH -tip 2/3] x86, mce: Revert "add mce=nopoll option to disable timer polling" Hidetoshi Seto
2009-04-20 7:26 ` Andi Kleen
2009-04-20 9:04 ` Hidetoshi Seto
2009-04-20 10:03 ` Andi Kleen [this message]
2009-04-20 10:45 ` [RESEND][PATCH -tip 2/3] x86, mce: Revert "add mce=nopoll option to disable timer polling"\ Hidetoshi Seto
2009-04-20 1:27 ` [RESEND][PATCH -tip 3/3] x86, mce: Add new option mce=no_cmci and mce=ignore_ce Hidetoshi Seto
2009-04-20 7:31 ` Andi Kleen
2009-04-20 9:05 ` Hidetoshi Seto
2009-04-22 3:25 ` [PATCH] x86, mce: Add options for corrected errors (no_cmci/dont_log_ce/ignore_ce) Hidetoshi Seto
2009-04-22 7:27 ` Andi Kleen
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=20090420100323.GW14687@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®