All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	sparky@bluefang-logic.com
Subject: Re: [PATCH] grub-mkconfig/10_linux: Support multiple early initrd images
Date: Sat, 17 Mar 2018 23:57:25 +0100	[thread overview]
Message-ID: <20180317235725.468a9871@leda> (raw)
In-Reply-To: <20180305164830.GD27749@router-fw-old.local.net-space.pl>

[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]

Daniel Kiper <dkiper@net-space.pl> on Mon, 2018/03/05 17:48:
> On Sat, Feb 24, 2018 at 05:44:58PM -0500, Matthew S. Turnbull wrote:
> > Add support for multiple, shared, early initrd images. These early
> > images will be loaded in the order declared, and all will be loaded
> > before the initrd image.
> >
> > While many classes of data can be provided by early images, the
> > immediate use case would be for distributions to provide CPU
> > microcode to mitigate the Meltdown and Spectre vulnerabilities.
> >
> > There are two environment variables provided for declaring the early
> > images.
> >
> > * GRUB_EARLY_INITRD_LINUX_STOCK is for the distribution declare
> >   images that are provided by the distribution or installed packages.
> >   If undeclared, this will default to a set of common microcode image
> >   names.
> >
> > * GRUB_EARLY_INITRD_LINUX_CUSTOM is for user created images. User
> >   images will be loaded after the stock images.
> >
> > These separate configurations allow the distribution and user to
> > declare different image sets without clobbering each other.
> >
> > This also makes a minor update to ensure that UUID partition labels
> > stay disabled when no initrd image is found, even if early images are
> > present.
> >
> > This is a continuation of a previous patch published by Christian
> > Hesse in 2016:
> > http://lists.gnu.org/archive/html/grub-devel/2016-02/msg00025.html
> >
> > Down stream Gentoo bug:
> > https://bugs.gentoo.org/645088
> >
> > Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
> > Signed-off-by: Matthew S. Turnbull <sparky@bluefang-logic.com>  
> 
> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
> 
> If there are not objections I will apply this in a week or so.

Thanks for picking my work and bringing this upstream! Much appreciated I can
use this now.
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-03-17 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 22:44 [PATCH] grub-mkconfig/10_linux: Support multiple early initrd images Matthew S. Turnbull
2018-03-05 16:48 ` Daniel Kiper
2018-03-17 22:57   ` Christian Hesse [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=20180317235725.468a9871@leda \
    --to=list@eworm.de \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=sparky@bluefang-logic.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.