From: "Bird, Tim" <Tim.Bird@sony.com>
To: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Reminder of boot-time SIG meeting for April
Date: Tue, 22 Apr 2025 01:54:41 +0000 [thread overview]
Message-ID: <MW5PR13MB5632DF2E1FE70ACD08E1586CFDBB2@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, April 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=04&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 April 22 meeting is:
- Round-table of on-going work
- Work on the Boot Time wiki (section of elinux wiki) https://elinux.org/Boot_Time
- Status of the Boot Time Data wiki (on birdcloud.org) https://birdcloud.org/boot-time/Boot_Data
- patches in flight:
- init/main.c: print initcall level when initcall_debug is used (Francesco Valla)
- analyze-initcall-debug.py (Francesco Valla)
- work pending submission upstream:
- show_delta version 2.0 (Tim Bird)
- deferred initcalls (Tim Bird)
- Are there any other patches in flight?
- What are people working on?
- deferred memory init (Qualcomm?)
- boot caching (the Good Penguin?)
- unified boot log (TI)
- CPU cycle counter logging (for firmware, kernel, user-space)
- Status of Sony boot-time work:
- boot time wiki (grab-boot-data.sh, boot-data repository, and BootRegion wiki processor)
- boot markers -> boot regions -> common printks (nothing published yet)
- Status of RedHat boot time work?
- [Eric] - patches submitted a couple of years ago - mounting volumes - might trigger errors
- Are currently tracking boot-time variances
- Status of Texas Instruments boot time work?
- [Vishnu] - update on work on boot markers (passing cycle-count timestamps between firmware and kernel)
- During startup, firmware runs on different processors, with different cycle-counters.
- Need generic mechanisms for handling tagging of timestamps, passing data between systems
- Status of Qualcomm deferred memory init patch?
- Qualcomm not on call, but TI is interested in seeing this, and other deferred init work, mainlined
- Review of project ideas
- See https://elinux.org/Boot_Time_Project_Ideas
- TGP (The Good Penguin) has some stuff they did with boot caching - see the page for details
- Review of action items
- Engaging more developers
- Next meeting - Tuesday, May 27, 9:00 am Mountain Daylight Time
- current periodicity = 1 month (the 4th Tuesday of every month
----
I look forward to talking with you in the meeting.
-- Tim
reply other threads:[~2025-04-22 2:51 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=MW5PR13MB5632DF2E1FE70ACD08E1586CFDBB2@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).