[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<MW5PR13MB56326559F5CBE58BB70CE24DFD5C2@MW5PR13MB5632.namprd13.prod.outlook.com>
Date: Thu, 7 Nov 2024 19:35:11 +0000
From: "Bird, Tim" <Tim.Bird@...y.com>
To: Saravana Kannan <saravanak@...gle.com>
CC: Brian Masney <bmasney@...hat.com>,
"linux-embedded@...r.kernel.org"
<linux-embedded@...r.kernel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: RE: Boot-time initiative (SIG) thoughts and next steps
> -----Original Message-----
> From: Saravana Kannan <saravanak@...gle.com>
> On Tue, Nov 5, 2024 at 4:45 PM Bird, Tim <Tim.Bird@...y.com> wrote:
[snip]
> > We should discuss what a kernel boot-time tuning guide should look like
> > and how it should be organized. Starting this may be one of the first
> > things the SIG does.
>
> I wrote something like this for the Android ecosystem
> https://source.android.com/docs/core/architecture/kernel/boot-time-opt
I just took a look at this and it looks like a very handy document.
I think having something like this in the upstream kernel doc would
be great.
> So, I'm happy to add something like this to the kernel doc if we have
> some consensus on having a kernel doc.
I don't hear any objections. I guess we'll get some feedback when we
post some patches to the linux-doc mailing list.
I would say go for it, and copy this list so we can discuss the planned
document format (and content, of course).
A lot of the information in the android doc would apply to the kernel doc.
-- Tim
Powered by blists - more mailing lists