From: Ingo Molnar <mingo@elte.hu>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Andi Kleen <ak@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Mike Travis <travis@sgi.com>
Subject: Re: [PATCH] x86, mce: short output of MCE banks ownership information
Date: Thu, 29 Oct 2009 08:34:08 +0100 [thread overview]
Message-ID: <20091029073408.GA18976@elte.hu> (raw)
In-Reply-To: <4AE93B42.5040605@jp.fujitsu.com>
* Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> wrote:
> Maybe there would be more desirable ways, but I think that "compress
> messages shorter to bear heavy repeating" will be a good way at this
> time.
We really want to only print out relevant information. 128 lines of
identical output is not relevant. (or 2x 64 lines, or 4096 lines of
identical output)
So we only want to print MCE setup messages on the boot CPU. That gives
us 90% of the benefits already: we see the rough structure of the
hardware, and if the bootup has a problem with MCE initialization we get
relevant printouts that helps debugging.
Now, it's certainly true that with things like MCE bank sharing the MCE
setup output from different CPUs might not be identical all the time -
but the information is represented in other (topology) info anyway. (and
if not it wasnt all that important to begin with)
For non-boot CPUs we can perhaps add a mce=verbose (default-disabled)
mode of bootup that allows all CPUs to be printed - should there be any
problem with MCE details only visible on non-boot CPUs. (unlikely)
Ingo
next prev parent reply other threads:[~2009-10-29 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 3:38 [PATCH] x86, mce: short output of MCE banks ownership information Hidetoshi Seto
2009-10-29 3:45 ` Roland Dreier
2009-10-29 6:50 ` Hidetoshi Seto
2009-10-29 7:34 ` Ingo Molnar [this message]
2009-10-29 8:27 ` Hidetoshi Seto
2009-10-29 9:09 ` Ingo Molnar
2009-10-29 16:07 ` Mike Travis
2009-10-29 16:00 ` Mike Travis
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=20091029073408.GA18976@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdreier@cisco.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
/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