From: caglarakyuz@gmail.com (Caglar Akyuz)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel Start-up Time
Date: Tue, 19 Jan 2010 16:35:41 +0200 [thread overview]
Message-ID: <201001191635.41944.caglarakyuz@gmail.com> (raw)
In-Reply-To: <20100119110408.GB9187@sig21.net>
On Tuesday 19 January 2010 01:04:08 pm Johannes Stezenbach wrote:
> On Mon, Jan 18, 2010 at 10:10:01AM +0200, Caglar Akyuz wrote:
> > While measuring Linux start-up time, I see that printing version string
> > in "start_kernel" takes ~1.3 seconds. I guess this is the time between
> > from "bootloader jumping to uImage" and "printing version string in
> > generic start_kernel code". Relevant part of my boot log is attached.
> >
> > My question: is it normal this 1.3 sec init time? My system is 297 MHZ
> > arm926ej-s with a 162MHZ DDR2 memory.
> >
> > [ 4.700896] Starting kernel ...
> > [ 4.702971]
> > [ 5.966039] [ 0.000000] Linux version
> > 2.6.30-davinci1-06079-g4e73fae-
>
> Actually printk goes to a buffer which is output only after the
> serial console has been initialized (unless you use some
> kind of early printk). So to find out what causes the delay
> look further down in your kernel messages, and look at the kernel
> timestamps not the ptx_ts ones.
>
I thought early prink was magically handling all this stuff. Passing
'earlyprintk' option to the kernel revealed correct numbers.
Caglar
>
> HTH
> Johannes
>
prev parent reply other threads:[~2010-01-19 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 8:10 Kernel Start-up Time Caglar Akyuz
2010-01-18 8:39 ` Tonyliu
2010-01-18 8:54 ` Caglar Akyuz
2010-01-18 15:39 ` Steve Chen
2010-01-18 19:39 ` Dirk Behme
2010-01-19 8:40 ` Caglar Akyuz
2010-01-19 8:36 ` Caglar Akyuz
2010-01-19 9:02 ` Russell King - ARM Linux
2010-01-19 14:31 ` Caglar Akyuz
2010-01-19 11:04 ` Bahadir Balban
2010-01-19 14:40 ` Caglar Akyuz
2010-01-19 11:04 ` Johannes Stezenbach
2010-01-19 14:35 ` Caglar Akyuz [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=201001191635.41944.caglarakyuz@gmail.com \
--to=caglarakyuz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.