From: Federico Giovanardi <federico@giovanardi.dev>
To: "Bird, Tim" <Tim.Bird@sony.com>
Cc: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: Deferred probe times
Date: Mon, 26 May 2025 10:14:33 +0200 [thread overview]
Message-ID: <acd79001bb4b436994aa920efa10c887@giovanardi.dev> (raw)
In-Reply-To: <MW5PR13MB56324F6600F6844DB8A6FCD5FD9BA@MW5PR13MB5632.namprd13.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Well, the comment about the giant block was not a complaint, of course.
With both patches, I used to get the attached image, so the
deferred_probe slot it's separated into its constituents.
Thanks
Federico
On 2025-05-24 02:16, Bird, Tim wrote:
>> -----Original Message-----
>> From: Federico Giovanardi <federico@giovanardi.dev>
>> Hello,
>>
>> I was poking around the boot data database while I noticed that the
>> deferred_probe initicalls are considered as a giant block;
>
> Hmm. I didn't think anyone was looking at this data besides myself.
> The site is really still under construction, so I apologize for missing
> and mis-formatted data. But thanks for looking at
> the data and finding something that needs attention upstream!!
>
>>
>> There is a patch that looks never went upstream to measure them:
>> https://lkml.iu.edu/1707.3/02349.html
>
> Wow, that's interesting. Here's the lore link for this thread:
> https://lore.kernel.org/lkml/20170725233159.89543-1-toddpoynor@google.com/#t
>
> It doesn't look like there were (after discussion) objections to
> accepting upstream.
> I wonder what happened.
>
> ...
> It looks like it was superceded by this patch:
> https://lore.kernel.org/lkml/20180620023903.242758-1-toddpoynor@gmail.com/
> which may provide some of the data necessary.
>
> The thing missing there are some (IMHO) better name lookups for the
> probe function.
> I wrote a patch for that, but didn't persist in trying to upstream it.
> Maybe I should
> dust that off and send it again.
>
>>
>> And another one from me to print the result in the .svg.
>>
>>
>> Have a nice day
>> Federico
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 73235 bytes --]
prev parent reply other threads:[~2025-05-26 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 7:56 Deferred probe times Federico Giovanardi
2025-05-24 0:16 ` Bird, Tim
2025-05-26 8:14 ` Federico Giovanardi [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=acd79001bb4b436994aa920efa10c887@giovanardi.dev \
--to=federico@giovanardi.dev \
--cc=Tim.Bird@sony.com \
--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 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).