From: "Bird, Tim" <Tim.Bird@sony.com>
To: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Boot-time presentations
Date: Wed, 23 Oct 2024 23:43:09 +0000 [thread overview]
Message-ID: <MW5PR13MB5632615B92A0D5ACAC24A702FD4D2@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)
Hello kernel developers,
I'm writing to inform you of some community-building initiatives I have planned
for embedded people interested in, or working on, boot time reduction for the kernel.
More specifically, I'm working on updating online resources on this topic, and
re-starting the use of some existing communication channels.
First thing: I've collected presentations and videos for the past several years on the topic
of boot time, on a page on the elinux wiki.
See this page: https://elinux.org/Boot_Time_Presentations
I plan to re-work and update the information on the boot time page on the elinux
wiki in the next few months. That page is here: https://elinux.org/Boot_Time
It needs a fair amount of work to update it for recent kernels and capture current areas of
activity. But even some of the old information there is useful now.
Second thing: I'm also trying to collect a list of developers who are actively working in this area,
as well as active areas of instrumentation, testing, patches, and techniques.
If you are interested in engaging in discussions about Linux boot time, the main thing to do
is be subscribed to linux-embedded@vger.kernel.org list. If you're reading this in an e-mail
client, instead of on lore, then you're all set. If not, you should consider subscribing to that
list. This linux-embedded mailing list is where I'll be announcing more about my work, and
trying to organize some collaboration in this space. You can also e-mail me privately if you
want to get on my list of "interested parties".
I'll be trying to set up some meetings and collaborative activities in the next few months.
I have a few patches I will be sending (such as my patch for 'deferred initcalls'), as well
as trying to build on some testing work that Collabora has already started (and releasing
my own tests of boot time, suitable for CI integration).
If you're in Japan, I'll be at Open Source Summit Japan in Tokyo next week. And I'd love
to meet up with you to discuss current work and future plans.
This is a follow-up from discussions held at Linux Plumbers Conference this year.
I hope to talk to you soon.
-- Tim Bird, Principal Software Engineer, Sony Electronics
reply other threads:[~2024-10-23 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MW5PR13MB5632615B92A0D5ACAC24A702FD4D2@MW5PR13MB5632.namprd13.prod.outlook.com \
--to=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 read-only IMAP folder(s) and NNTP newsgroup(s).