mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: "Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
	linux-kernel@vger.kernel.org,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Guido Martínez" <guido@vanguardiasur.com.ar>
Subject: Re: [PATCH] init: Introduce 'noinitramfs' kernel parameter
Date: Sun, 22 Jun 2014 21:08:47 -0300	[thread overview]
Message-ID: <20140623000847.GA31648@khazad-dum.debian.net> (raw)
In-Reply-To: <20140622212959.GA766@arch.cereza>

On Sun, 22 Jun 2014, Ezequiel Garcia wrote:
> On 22 Jun 11:53 AM, Henrique de Moraes Holschuh wrote:
> > On Sun, 22 Jun 2014, Ezequiel Garcia wrote:
> > > This commit adds a new kernel parameter to provide such option, following the
> > > naming of the current 'initrd' which serves a similar purpose, for an initial
> > > RAM disk.
> > 
> > How does it interact with the early initramfs?
> > 
> > Maybe we should have the options to ignore both, ignore just the early
> > initramfs (to skip microcode updates and ACPI table updates), and ignore
> > just the main initramfs?
> > 
> 
> I must admit I don't have much experience with any "earlier" initramfs.
> Maybe you can point me at some links about this?

Search for kernel code that includes the linux/earlycpio.h header file.  The
implementation is at lib/earlycpio.c.

I am sorry I don't have a better reference to point you to.

> Unless I'm missing something, this "early" initramfs is an userspace artifact
> in the construction of the initramfs, so the kernel has no way to distinguish

No, it is an uncompressed cpio archive which is parsed extremely early, for
critical system firmware (currently: processor microcode updates and ACPI
table overrides).

Documentation of its two current users is at:

Documentation/x86/early-microcode.txt
Documentation/acpi/initrd_table_override.txt

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

      reply	other threads:[~2014-06-23  0:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22  5:41 Ezequiel Garcia
2014-06-22 14:53 ` Henrique de Moraes Holschuh
2014-06-22 21:30   ` Ezequiel Garcia
2014-06-23  0:08     ` Henrique de Moraes Holschuh [this message]

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=20140623000847.GA31648@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=akpm@linux-foundation.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=guido@vanguardiasur.com.ar \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®