From: Xie XiuQi <xiexiuqi@huawei.com>
To: Younger Liu <younger.liucn@gmail.com>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question: Takes about 2s in sched_clock_init() when kernel boots
Date: Thu, 31 Oct 2013 14:12:57 +0800 [thread overview]
Message-ID: <5271F4E9.8010709@huawei.com> (raw)
In-Reply-To: <5271EAAC.7080304@gmail.com>
On 2013/10/31 13:29, Younger Liu wrote:
> Hi,
> When I analyse boot time on ArmV7, I found that it takes
> about 2s in sched_clock_init(), the log is as follow:
> [ 0.000000] before:sched_clock_init.
> [ 0.000000] start:sched_clock_init.
> [ 2.100505] end :sched_clock_init.
> [ 2.103983] before:calibrate_delay.
>
> In my config, CONFIG_HAVE_UNSTABLE_SCHED_CLOCK does not config.
>
> Are there any suggestions?
see below:
u64 sched_clock_cpu(int cpu)
{
struct sched_clock_data *scd;
u64 clock;
WARN_ON_ONCE(!irqs_disabled());
if (sched_clock_stable)
return sched_clock();
if (unlikely(!sched_clock_running))
return 0ull;
scd = cpu_sdc(cpu);
[...]
Unless sched_clock_running is set, it'll return 0. So, the
printk() time stamp is 0 before sched_clock_init calling.
>
> Younger
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2013-10-31 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 5:29 Question: Takes about 2s in sched_clock_init() when kernel boots Younger Liu
2013-10-31 6:12 ` Xie XiuQi [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=5271F4E9.8010709@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=younger.liucn@gmail.com \
/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