From: Andi Kleen <ak@linux.intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 1/3] x86, mce: Add mce_threshold option for intel cmci
Date: Tue, 31 Mar 2009 10:08:00 +0200 [thread overview]
Message-ID: <49D1CF60.5020107@linux.intel.com> (raw)
In-Reply-To: <49D183BA.5020007@jp.fujitsu.com>
Hidetoshi Seto wrote:
> Andi Kleen wrote:
>> To turn it off you would need to disable the CMCI enable bit
>> completely.
>
> mce_threshold=0 discourages CMCI initialization.
> The CMCI enable bits are kept in off states in this case.
True, I missed that earlier. Still a different option would be better.
>
>> However I expect that this will be not a good idea to ever use on Nehalem
>> class systems at least because without CMCI the machine check code cannot
>> handle shared banks correctly and you'll get duplicated events from them.
>> And on non Nehalem systems there is no CMCI anyways, so it'll be always
>> off.
>
> One question is that even if one clears record in a shared bank, others
> sharing the bank still can retrieve same record? Or the duplication of
> recored only happens if a shared bank is polled by multiple cpu in parallel
> at same time?
Only when multiple CPUs poll (or machine check) at the same time.
>
> So old kernel without CMCI support running on new Nehalem class system will
> make duplicated records, right?
Occasionally when it races yes.
> Doesn't it impact to current distro like RHEL5?
Yes, somewhat. The bigger problem there is actually lack of broadcast handling,
that often leads to incorrect reporting of fatal MCEs.
-Andi
next prev parent reply other threads:[~2009-03-31 8:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 8:39 [PATCH -tip 1/3] x86, mce: Add mce_threshold option for intel cmci Hidetoshi Seto
2009-03-26 9:10 ` Andi Kleen
2009-03-27 9:44 ` Hidetoshi Seto
2009-03-27 10:31 ` Andi Kleen
2009-03-30 9:06 ` Hidetoshi Seto
2009-03-30 10:05 ` Andi Kleen
2009-03-31 7:22 ` Hidetoshi Seto
2009-03-31 8:15 ` Andi Kleen
2009-03-28 12:00 ` Ingo Molnar
2009-03-28 12:08 ` Ingo Molnar
2009-03-30 9:42 ` Andi Kleen
2009-03-31 2:45 ` Hidetoshi Seto
2009-03-31 8:08 ` Andi Kleen [this message]
2009-03-31 2:45 ` Hidetoshi Seto
2009-04-01 15:07 ` Ingo Molnar
2009-04-02 4:43 ` Hidetoshi Seto
2009-04-02 4:54 ` [PATCH -tip 1/3] x86, mce: Revert "add mce_threshold option for intel cmci" Hidetoshi Seto
2009-04-02 4:55 ` [PATCH -tip 2/3] x86, mce: Revert "add mce=nopoll option to disable timer polling" Hidetoshi Seto
2009-04-02 4:58 ` [PATCH -tip 3/3] x86, mce: Add new option mce=no_cmci and mce=ignore_ce Hidetoshi Seto
2009-03-28 21:28 ` [tip:x86/mce2] x86, mce: Add mce_threshold option for intel cmci 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=49D1CF60.5020107@linux.intel.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.