linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bird, Tim" <Tim.Bird@sony.com>
To: Linux Embedded <linux-embedded@vger.kernel.org>
Subject: [boot-time] Reminder of Boot-Time SIG meeting (July 22)
Date: Thu, 17 Jul 2025 22:56:58 +0000	[thread overview]
Message-ID: <MW5PR13MB563270DA8DEAA70ED3DD5D55FD51A@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)

Hey Linux Boot-Time SIG interested parties (and other interested Linux kernel developers),

Here is the information for the next Linux Boot-Time SIG conference call.

The meeting will be held via the Jitsi online meeting platform.
To Join the meeting via web, click on:
https://meet.jit.si/LinuxBootTimeSIG

----
Our next meeting is Tuesday, July 22, at 9:00 am Mountain Daylight Time.
See this link for other time zones:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2025&month=07&day=22&hour=15&min=0&sec=0&p1=220&p2=137&p3=195&p4=771
(That makes it 8:00 am Pacific, 15:00 UTC, 17:00 CET, and 20:30 IST)

I'm planning on 1 hour for this meeting.

The agenda for the meeting (and where we'll keep the minutes) is here:
https://docs.google.com/document/d/1XAufoTT6VVJOTMzKMoz8SyOss-JA9H4J1_yVXQq5mN0/edit?usp=sharing

The agenda for the July 22 meeting will be available in the above document before the call.
This is what I've got so far:

- ELC boot-time post-mortem
   - What ideas should we follow up on to advance upstream?

  - Status of patches or docs being considered for upstream
    - print initlevel
    - bootstage stash driver
    - show_delta 2.0
    - deferred initcalls
    - better probe details (function name, to map to source line)
    - pre-timer init cycle count durations (and tool)
    - anything outstanding for deferred memory init?
    - documentation or tuning guide?

- Round-table of on-going work
     - Tim currently working on:
         - boot time early cycle counts (Tim)
         - boot-time regression test
         - mapping printks and initcalls to source lines, to accumulate boot time per Linux sub-system
   - boot caching (The Good Penguin work)
   - boot-time data wiki (Tim)
   - Unified Boot Log (Vishnu, TI)
   - elinux wiki Boot-Time pages
      - https://elinux.org/Boot_Time_Project_Ideas
    - Automatically reducing kernel configuration (Michael)
    - Android working on parallelized module loading (Saravana)
    - some udev integration with systemd (Federico)
     
 - Conference and meetups:
   - ELC 2025 - June 23-25, Denver, USA - pretty good lineup of boot-time topics
     - presentations and videos are now available: https://elinux.org/ELC_2025_Presentations
   - ELCE 2025 - August 25-27, Amsterdam, The Netherlands
   - LPC 2026 - December 11-13, 2025, Tokyo, Japan

Next meeting: August 26th falls during Embedded Linux Conference Europe 2025,
so we'll skip that as a call.  If there's enough interest, we might be able to schedule an unconference
session for boot-time discussions in Amsterdam, for those present.
Our next call will likely be September 23rd.

--------

If you have items you'd like to cover, please e-mail me or put them in the document.

Thanks,
 -- Tim


                 reply	other threads:[~2025-07-17 23:56 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=MW5PR13MB563270DA8DEAA70ED3DD5D55FD51A@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).