linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: caglarakyuz@gmail.com (Caglar Akyuz)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel Start-up Time
Date: Tue, 19 Jan 2010 16:40:43 +0200	[thread overview]
Message-ID: <201001191640.43715.caglarakyuz@gmail.com> (raw)
In-Reply-To: <4B5591A4.2050807@l4dev.org>

On Tuesday 19 January 2010 01:04:04 pm Bahadir Balban wrote:
> Caglar Akyuz wrote:
> > Hello,
> >
> > 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".
> >
> > Thanks,
> > Caglar
> >
> > _____________________________________________________________________
> >
> > [    4.700896] Starting kernel ...
> > [    4.702971]
> > [    5.966039] [    0.000000] Linux version
> > 2.6.30-davinci1-06079-g4e73fae-
> 
> Hi Caglar,
> 
> This sounds like the kernel decompression is taking time. Have you tried
> booting an uncompressed kernel? See if you can print on physical uart
> address from files under arch/arm/boot/compressed
> 
> Thanks,
> 

Hi,

My image was uncompressed already. However, I was fooled by the printk delays. 
Learning proper use of early printk solved the issue.

Thanks,
Caglar

  reply	other threads:[~2010-01-19 14:40 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 [this message]
2010-01-19 11:04 ` Johannes Stezenbach
2010-01-19 14:35   ` Caglar Akyuz

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=201001191640.43715.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 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).