From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: init_kprobes() takes too much time during boot up
Date: Thu, 22 Dec 2011 22:20:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1112222212140.2907@xanadu.home> (raw)
In-Reply-To: <CAMPhdO8T5wwPBYp_n15A88o8YxkXv2t8WOumRyni6WDhJinS3A@mail.gmail.com>
On Fri, 23 Dec 2011, Eric Miao wrote:
> I was trying to improve the kernel boot performance of the boards at
> my hands, while simply turning on initcall_debug, and found that
> init_kprobes() won the crown of being the most hungry time gobbler.
>
> Before I take my time to look into why it's taking so much time, I'd
> post the question to the list to seek help first.
>From a quick glance, the "Lookup and populate the kprobe_blacklist"
loops certainly have the potential to be costly.
There is nothing with notable complexity in the ARM specific part.
CC'ing Tixy in case he has a better idea.
Nicolas
next prev parent reply other threads:[~2011-12-23 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 3:06 init_kprobes() takes too much time during boot up Eric Miao
2011-12-23 3:20 ` Nicolas Pitre [this message]
2011-12-23 11:54 ` Jon Medhurst (Tixy)
2012-01-03 9:09 ` Russell King - ARM Linux
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=alpine.LFD.2.02.1112222212140.2907@xanadu.home \
--to=nicolas.pitre@linaro.org \
--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).