From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [DMESG] cpumask_t in action
Date: Thu, 06 Nov 2003 18:56:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106814524713112@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106807117402763@msgid-missing>
> That'd cut us down to:
>
> > CPU 3: 61 virtual and 50 physical address bits
> > CPU 3: nasid 2, slice 2, cnode 1
> > CPU 3: base freq 0.000MHz, ITC ratio\x15/2, ITC freq\x1500.000MHz+/--1ppm
> > Calibrating delay loop... 2241.08 BogoMIPS
> > CPU3: CPU has booted.
> > Starting migration thread for cpu 3
Perhaps we could drop printing the number of virtual/physical address
bits, and the frequency&ratio information (or maybe just print if they
are different from the boot cpu ... which would most likely surprise
the kernel in bad ways, and thus be worthy of printing). That would
cut another two lines for all bar one cpu.
-Tony
next prev parent reply other threads:[~2003-11-06 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 22:22 [DMESG] cpumask_t in action Jesse Barnes
2003-11-05 23:18 ` Chen, Kenneth W
2003-11-06 16:51 ` Matthew Wilcox
2003-11-06 17:20 ` Jesse Barnes
2003-11-06 17:23 ` Jesse Barnes
2003-11-06 18:56 ` Luck, Tony [this message]
2003-11-06 20:11 ` Jes Sorensen
2003-11-06 20:31 ` Robin Holt
2003-11-07 2:06 ` Paul Jackson
2003-11-07 8:13 ` Sylvain Jeaugey
2003-11-07 17:24 ` Matthew Wilcox
2003-11-10 8:26 ` Jes Sorensen
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=marc-linux-ia64-106814524713112@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@vger.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