From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] enhance initcall_debug, measure latency
Date: Mon, 2 Apr 2007 08:04:08 +0200 [thread overview]
Message-ID: <20070402060408.GA6505@elte.hu> (raw)
In-Reply-To: <20070401182801.GA25956@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> some boot time analysis using this facility:
using a non-allyesconfig kernel gives the results below. The entries
that seem to take a bit too long (considering what they do):
initcall 0xc069bac5 ran for 519 msecs: init_nic+0x0/0x2c()
initcall 0xc0699610 ran for 344 msecs: isapnp_init+0x0/0x435()
initcall 0xc069af66 ran for 245 msecs: serial8250_init+0x0/0x112()
initcall 0xc06981e8 ran for 183 msecs: acpi_pci_link_init+0x0/0x43()
initcall 0xc06a07b0 ran for 175 msecs: pci_acpi_init+0x0/0x9b()
initcall 0xc06980ef ran for 110 msecs: acpi_pci_root_init+0x0/0x25()
initcall 0xc069fa24 ran for 69 msecs: pcibios_assign_resources+0x0/0x92()
initcall 0xc0246fd6 ran for 64 msecs: pci_init+0x0/0x2c()
initcall 0xc0695fc2 ran for 62 msecs: pcie_portdrv_init+0x0/0x46()
initcall 0xc0698656 ran for 54 msecs: pnp_system_init+0x0/0xf()
initcall 0xc06a27ac ran for 43 msecs: inet_init+0x0/0x390()
initcall 0xc069f88e ran for 28 msecs: init_acpi_pm_clocksource+0x0/0x173()
these amount to almost 50% of the ~4 seconds total bootup initcall time!
Ingo
initcall 0xc069c43b ran for 1147 msecs: ide_init+0x0/0x8a()
initcall 0xc069bac5 ran for 519 msecs: init_nic+0x0/0x2c()
initcall 0xc069cbe0 ran for 497 msecs: ide_generic_init+0x0/0x11()
initcall 0xc0699610 ran for 344 msecs: isapnp_init+0x0/0x435()
initcall 0xc069af66 ran for 245 msecs: serial8250_init+0x0/0x112()
initcall 0xc06981e8 ran for 183 msecs: acpi_pci_link_init+0x0/0x43()
initcall 0xc06a07b0 ran for 175 msecs: pci_acpi_init+0x0/0x9b()
initcall 0xc06980ef ran for 110 msecs: acpi_pci_root_init+0x0/0x25()
initcall 0xc068b878 ran for 97 msecs: check_nmi_watchdog+0x0/0x1d1()
initcall 0xc069cbf1 ran for 75 msecs: idedisk_init+0x0/0xf()
initcall 0xc069fa24 ran for 69 msecs: pcibios_assign_resources+0x0/0x92()
initcall 0xc0246fd6 ran for 64 msecs: pci_init+0x0/0x2c()
initcall 0xc0695fc2 ran for 62 msecs: pcie_portdrv_init+0x0/0x46()
initcall 0xc0698656 ran for 54 msecs: pnp_system_init+0x0/0xf()
initcall 0xc06a27ac ran for 43 msecs: inet_init+0x0/0x390()
initcall 0xc069f88e ran for 28 msecs: init_acpi_pm_clocksource+0x0/0x173()
initcall 0xc069bb07 ran for 23 msecs: rtl8139_init_module+0x0/0x16()
initcall 0xc069eeae ran for 18 msecs: psmouse_init+0x0/0x64()
initcall 0xc0111a26 ran for 18 msecs: powernowk8_init+0x0/0x78()
initcall 0xc069e932 ran for 17 msecs: i8042_init+0x0/0x321()
initcall 0xc069baf1 ran for 16 msecs: cp_init+0x0/0x16()
initcall 0xc06979b8 ran for 16 msecs: acpi_init+0x0/0x1ff()
initcall 0xc0697bfc ran for 15 msecs: acpi_scan_init+0x0/0xfc()
initcall 0xc06a3154 ran for 12 msecs: netlbl_init+0x0/0x71()
initcall 0xc069e512 ran for 11 msecs: usb_init+0x0/0x103()
initcall 0xc06986cd ran for 11 msecs: pnpacpi_init+0x0/0x69()
next prev parent reply other threads:[~2007-04-02 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 18:16 Ingo Molnar
2007-04-01 18:28 ` Ingo Molnar
2007-04-02 6:04 ` Ingo Molnar [this message]
2007-04-02 8:00 ` Andi Kleen
2007-04-02 7:09 ` Ingo Molnar
2007-04-02 7:22 ` Andi Kleen
2007-04-02 5:50 ` Andrew Morton
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=20070402060408.GA6505@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®