From: Yinghai Lu <yinghai@kernel.org>
To: Robin Holt <holt@sgi.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC 2/2] Make x86 calibrate_delay run in parallel.
Date: Thu, 31 Mar 2011 07:25:05 -0700 [thread overview]
Message-ID: <4D948EC1.9080208@kernel.org> (raw)
In-Reply-To: <20110331092945.GD24046@sgi.com>
On 03/31/2011 02:29 AM, Robin Holt wrote:
...
> I don't see how this patch would affect that. Has this been tested on
> a multi-core intel cpu? I will try to test it today when I get to the
> office.
Yes. I tested on our 8 sockets 10 cores intel cpu system and 8 cores system.
looks getting correct result.
>
> Additionally, it takes the bogomips value from being part of an output
> line and makes it a separate line. On a 4096 cpu system, that will mean
> many additional lines of output. In the past, we have seen that will
> cause a considerable slowdown as time is spent printing. Fortunately,
> that is likely not going to slow things down as a secondary cpu will
> likely be doing that work while the boot cpu is allowed to continue with
> the boot. Is there really a value for a normal boot to have this output?
> Can we remove the individual lines of output and just print the system
> BogoMips value?
that is easy. just update print_lpj.
static void __cpuinit print_lpj(int cpu, char *str, unsigned long lpj)
{
static bool printed;
if (printed)
return;
pr_info("CPU%d: Calibrating delay%s"
"%lu.%02lu BogoMIPS (lpj=%lu)\n", cpu, str,
lpj/(500000/HZ), (lpj/(5000/HZ)) % 100, lpj);
/* only print cpu0, and cpu1 */
if (cpu)
printed = true;
}
current printing is for debug purpose, So we don't need to waiting the booting get done.
just checking it serial console.
Thanks
Yinghai
prev parent reply other threads:[~2011-03-31 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 1:58 [RFC 0/2] Speed large x86_64 system boot by calling calibrate_delay() in parallel Robin, Holt <holt
2010-12-15 1:58 ` [RFC 1/2] Pass loops_per_jiffy in and out of calibrate_delay() Robin, Holt <holt
2010-12-15 1:58 ` [RFC 2/2] Make x86 calibrate_delay run in parallel Robin, Holt <holt
2010-12-16 8:34 ` Thomas Gleixner
2011-03-31 4:46 ` Yinghai Lu
2011-03-31 6:50 ` Ingo Molnar
2011-03-31 6:58 ` Ingo Molnar
2011-03-31 9:37 ` Robin Holt
2011-03-31 9:57 ` Ingo Molnar
2011-03-31 10:30 ` Avi Kivity
2011-03-31 10:46 ` Ingo Molnar
2011-03-31 10:49 ` Avi Kivity
2011-03-31 11:13 ` Ingo Molnar
2011-03-31 11:50 ` Robin Holt
2011-03-31 9:29 ` Robin Holt
2011-03-31 14:25 ` Yinghai Lu [this message]
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=4D948EC1.9080208@kernel.org \
--to=yinghai@kernel.org \
--cc=andi@firstfloor.org \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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