From: Francesco Valla <francesco@valla.it>
To: "Bird, Tim" <Tim.Bird@sony.com>,
Stephan Mueller <smueller@chronox.de>,
Shankari <beingcap11@gmail.com>, Rob Landley <rob@landley.net>
Cc: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: boot markers ideas (was RE: [boot-time] jent_mod_init on beagleplay)
Date: Thu, 09 Jan 2025 17:23:04 +0100 [thread overview]
Message-ID: <2161392.9o76ZdvQCi@fedora.fritz.box> (raw)
In-Reply-To: <211b015d-44e5-4e64-9e44-5968d86dfac4@landley.net>
Hello Rob,
On Wednesday, 8 January 2025 at 00:40:13 Rob Landley <rob@landley.net> wrote:
> Is there a place to get this measuring script other than fishing it out
> of a webmail archive?
>
> https://www.spinics.net/lists/linux-embedded/msg04363.html
No, at the moment the mailing list is the only place I posted it. I am still
unsure if it should live on its own somewhere or it's better to try to augment
the bootchart.py script that lives inside the kernel sources [1].
> The most recent wiki mention in the archive subject lines was
> https://www.spinics.net/lists/linux-embedded/msg04336.html and trying to
> find this effort in elinux.org's top right search bar found
> https://elinux.org/Boot-up_Time_Reduction_Howto which "view history"
> says was last touched in 2010...
>
> Rob
>
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/pm-graph/bootgraph.py
Regards,
Francesco
next prev parent reply other threads:[~2025-01-09 17:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 23:35 [boot-time] [RFC] analyze-initcall-debug.py - a tool to analyze the initcall debug output Francesco Valla
2024-12-03 20:33 ` Bird, Tim
2024-12-05 12:57 ` Francesco Valla
2024-12-05 14:58 ` Geert Uytterhoeven
2024-12-05 21:36 ` Francesco Valla
2024-12-09 3:10 ` [RFC PATCH] boot-time: instrument probes more Bird, Tim
2024-12-21 14:47 ` Francesco Valla
2024-12-29 17:45 ` Francesco Valla
2024-12-03 21:24 ` [boot-time] jent_mod_init on beagleplay (was RE: [boot-time] [RFC] analyze-initcall-debug.py - a tool to analyze the initcall debug output Bird, Tim
2024-12-05 7:02 ` Stephan Mueller
[not found] ` <CAORPcfUfgNnQb6m0baW9qEGnrGYsnbpvwUUmF5Y9Byh9_iMAZw@mail.gmail.com>
2024-12-30 22:35 ` Francesco Valla
2024-12-31 9:55 ` Stephan Müller
2024-12-31 14:42 ` Francesco Valla
2025-01-02 9:06 ` Stephan Mueller
2025-01-02 10:33 ` Francesco Valla
2025-01-02 12:56 ` Stephan Mueller
2025-01-03 17:23 ` Francesco Valla
2025-01-04 15:45 ` Stephan Müller
2025-01-07 22:40 ` Bird, Tim
2025-01-07 21:42 ` boot markers ideas (was RE: [boot-time] jent_mod_init on beagleplay) Bird, Tim
2025-01-07 23:40 ` Rob Landley
2025-01-09 16:23 ` Francesco Valla [this message]
2024-12-30 22:22 ` [boot-time] jent_mod_init on beagleplay (was RE: [boot-time] [RFC] analyze-initcall-debug.py - a tool to analyze the initcall debug output Francesco Valla
2025-01-07 21:27 ` Bird, Tim
2024-12-04 0:29 ` Bird, Tim
2024-12-05 13:05 ` Francesco Valla
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=2161392.9o76ZdvQCi@fedora.fritz.box \
--to=francesco@valla.it \
--cc=Tim.Bird@sony.com \
--cc=beingcap11@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=rob@landley.net \
--cc=smueller@chronox.de \
/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).