From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: Why call calibrate_delay() in smp.c: secondary_start_kernel()
Date: Tue, 18 Jan 2011 15:46:54 +0530 [thread overview]
Message-ID: <ebe9b3d6a0cc160cd46a97ae05b72119@mail.gmail.com> (raw)
In-Reply-To: <4D3552C2.3020101@stericsson.com>
> -----Original Message-----
> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-
> arm-kernel-bounces at lists.infradead.org] On Behalf Of Jonas Aaberg
> Sent: Tuesday, January 18, 2011 2:14 PM
> To: linux-arm-kernel at lists.infradead.org
> Cc: STEricsson_nomadik_linux
> Subject: Why call calibrate_delay() in smp.c:
> secondary_start_kernel()
>
>
> Hi,
>
> calibrate_delay() calculates loops_per_jiffy. loops_per_jiffy is not
> per cpu.
> Therefore I wonder why there is a calibrate_delay() call in smp.c:
> secondary_start_kernel()?
>
> If you don't set lpj= it looks like it just takes longer time to
> boot
> and bring a secondary cpu online.
>
> u8500 seems to do fine without the calibrate_delay() call.
>
I did send a patch on the same some time back but the conclusion
was we still need to have calibration.
Have one more patch do deal with it so that platform can choose
if they like to skip. My mailer might screw the patch hence attaching
the same
next prev parent reply other threads:[~2011-01-18 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 8:43 Why call calibrate_delay() in smp.c: secondary_start_kernel() Jonas Aaberg
2011-01-18 10:16 ` Santosh Shilimkar [this message]
2011-01-18 11:31 ` Russell King - ARM Linux
2011-01-18 12:12 ` Santosh Shilimkar
2011-01-18 12:16 ` Russell King - ARM Linux
2011-01-18 12:25 ` Santosh Shilimkar
2011-01-18 15:17 ` Linus Walleij
2011-01-18 15:30 ` Santosh Shilimkar
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=ebe9b3d6a0cc160cd46a97ae05b72119@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).