From: Federico Giovanardi <federico@giovanardi.dev>
To: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Deferred probe times
Date: Fri, 23 May 2025 09:56:00 +0200 [thread overview]
Message-ID: <cd10fd7ee9a3b0ce61cf3c1ea3805fbd@giovanardi.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
Hello,
I was poking around the boot data database while I noticed that the
deferred_probe initicalls are considered as a giant block;
There is a patch that looks never went upstream to measure them:
https://lkml.iu.edu/1707.3/02349.html
And another one from me to print the result in the .svg.
Have a nice day
Federico
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: update_bootgraph_deferred_init.patch --]
[-- Type: text/x-diff; name=update_bootgraph_deferred_init.patch, Size: 961 bytes --]
commit c8d97bad2987b33b2ce804805071218fd7f68bbd
Author: Federico Giovanardi <federico.giovanardi@cnhind.com>
Date: Fri Oct 4 14:13:30 2024 +0200
Update bootgraph to handle deferred initcalls
diff --git a/scripts/bootgraph.pl b/scripts/bootgraph.pl
index 79c903292ae8..8057d9f474df 100755
--- a/scripts/bootgraph.pl
+++ b/scripts/bootgraph.pl
@@ -67,7 +67,8 @@ my $cyheader = 0;
while (<>) {
my $line = $_;
- if ($line =~ /([0-9\.]+)\] calling ([a-zA-Z0-9\_\.]+)\+/) {
+ if ($line =~ /([0-9\.]+)\] calling ([a-zA-Z0-9\_\.]+)\+/ or
+ $line =~ /([0-9\.]+)\] deferred probe ([a-zA-Z0-9\_\.]+) @/) {
my $func = $2;
if ($done == 0) {
$start{$func} = $1;
@@ -109,6 +110,12 @@ while (<>) {
$maxtime = $1;
}
}
+ if ($line =~ /([0-9\.]+)\] deferred probe ([a-zA-Z0-9\_\.]+).*returned/) {
+ if ($done == 0) {
+ $end{$2} = $1;
+ $maxtime = $1;
+ }
+ }
if ($line =~ /([0-9\.]+)\] async_continuing @ ([0-9]+)/) {
my $pid = $2;
next reply other threads:[~2025-05-23 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 7:56 Federico Giovanardi [this message]
2025-05-24 0:16 ` Deferred probe times Bird, Tim
2025-05-26 8:14 ` Federico Giovanardi
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=cd10fd7ee9a3b0ce61cf3c1ea3805fbd@giovanardi.dev \
--to=federico@giovanardi.dev \
--cc=linux-embedded@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 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.