[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6332a54e-74c6-eafd-368e-71e87a3fa34e@landley.net>
Date: Tue, 13 Sep 2016 21:38:17 -0500
From: Rob Landley <rob@...dley.net>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Felix Fietkau <nbd@....name>,
David Woodhouse <dwmw2@...radead.org>,
Roman Pen <r.peniaev@...il.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Ming Lei <ming.lei@...onical.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Marek <mmarek@...e.com>,
Greg KH <gregkh@...uxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Vikram Mulukutla <markivx@...eaurora.org>,
Stephen Boyd <stephen.boyd@...aro.org>,
Mark Brown <broonie@...nel.org>, Takashi Iwai <tiwai@...e.de>,
Johannes Berg <johannes@...solutions.net>,
Christian Lamparter <chunkeey@...glemail.com>,
hauke@...ke-m.de, Josh Boyer <jwboyer@...oraproject.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>, jslaby@...e.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Wu Fengguang <fengguang.wu@...el.com>, rpurdie@...ys.net,
Jeff Mahoney <jeffm@...e.com>, j.anaszewski@...sung.com,
Abhay_Salunke@...l.com, Julia Lawall <Julia.Lawall@...6.fr>,
Gilles.Muller@...6.fr, nicolas.palix@...g.fr,
Tom Gundersen <teg@...m.no>, Kay Sievers <kay@...y.org>,
David Howells <dhowells@...hat.com>,
Alessandro Rubini <rubini@...dd.com>,
Kevin Cernekee <cernekee@...il.com>,
Kees Cook <keescook@...omium.org>,
Jonathan Corbet <corbet@....net>,
Thierry Martinez <martinez@...p.org>, cocci@...teme.lip6.fr,
linux-serial@...r.kernel.org, linux-doc@...r.kernel.org,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [RFC] fs: add userspace critical mounts event support
On 09/02/2016 07:20 PM, Luis R. Rodriguez wrote:
> kernel_read_file_from_path() can try to read a file from
> the system's filesystem. This is typically done for firmware
> for instance, which lives in /lib/firmware. One issue with
> this is that the kernel cannot know for sure when the real
> final /lib/firmare/ is ready, and even if you use initramfs
> drivers are currently initialized *first* prior to the initramfs
> kicking off.
Why?
> During init we run through all init calls first
> (do_initcalls()) and finally the initramfs is processed via
> prepare_namespace():
What's the downside of moving initramfs cpio extraction earlier in the boot?
I did some shuffling around of those code to make initmpfs work, does
anybody know why initramfs extraction _before_ we initialize drivers
would be a bad thing? (The cpio is in memory, either linked into the
kernel or from the bootloader. No drivers are needed to extract it,
that's sort of the point.)
The only things I can think of are memory churn (large contiguous
physical page allocations), or if a driver somehow got us access to more
physical memory?
Rob
Powered by blists - more mailing lists