From: Dave Jones <davej@redhat.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH][2.6-mm] Make i386 boot not so chatty
Date: Fri, 21 May 2004 13:10:21 +0100 [thread overview]
Message-ID: <20040521121021.GA23750@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405210101200.2864@montezuma.fsmlabs.com>
On Fri, May 21, 2004 at 01:06:23AM -0400, Zwane Mwaikambo wrote:
> Processor #0 5:2 APIC version 16
> Processor #3 5:2 APIC version 16
> Processor #4 5:2 APIC version 16
I'd argue these are of little value as long as they work.
(and we printk a different message iirc if they are unknown to us)
> Enabling APIC mode: Flat. Using 2 I/O APICs
ditto
> Processors: 3
a 3-way? cute.
> Built 1 zonelists
useful ?
> kernel profiling enabled
feh. if we cared, we could check /proc/profile or
look for oprofilefs
> PID hash table entries: 1024 (order 10: 8192 bytes)
kern_debug ?
> Calibrating delay loop... 254.97 BogoMIPS
yawn
> POSIX conformance testing by UNIFIX
I thought this got nuked already
> Calibrating delay loop... 266.24 BogoMIPS
> Calibrating delay loop... 265.21 BogoMIPS
> Total of 3 processors activated (786.43 BogoMIPS).
Maybe just keep the last line ? kern_boring the others.
Dave
next prev parent reply other threads:[~2004-05-21 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 4:46 [PATCH][2.6-mm] Make i386 boot not so chatty Zwane Mwaikambo
2004-05-21 5:06 ` Zwane Mwaikambo
2004-05-21 12:10 ` Dave Jones [this message]
2004-05-21 15:19 ` Zwane Mwaikambo
2004-05-21 6:40 ` Andrew Morton
2004-05-21 15:14 ` Zwane Mwaikambo
2004-05-22 12:01 ` Ed Tomlinson
2004-05-24 15:54 ` Randy.Dunlap
2004-05-22 14:43 ` Bill Davidsen
2004-05-24 10:12 ` Pavel Machek
2004-05-27 19:39 ` Miquel van Smoorenburg
[not found] <1Yaiz-33L-1@gated-at.bofh.it>
2004-05-21 10:29 ` Andi Kleen
2004-05-21 15:13 ` Zwane Mwaikambo
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=20040521121021.GA23750@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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