Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 22 Jun 2020 17:01:45 -0400
From:   Tom Rini <trini@konsulko.com>
To:     ron minnich <rminnich@gmail.com>
Cc:     lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Borislav Petkov <bp@suse.de>,
        Dominik Brodowski <linux@dominikbrodowski.net>,
        "H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] initrd: Remove erroneous comment
Message-ID: <20200622210145.GM27801@bill-the-cat>
References: <20200619143056.24538-1-trini@konsulko.com>
 <CAP6exYJ64Hy9y3Dzh9Asrq8Y0oDWYk+tf4UAcasEc-ZxTY8DAw@mail.gmail.com>
 <20200622204034.GL27801@bill-the-cat>
 <CAP6exYLd0uFbVSbn28iS1OV=jULtg2f+7t1DAn-fvGoRSd5dng@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="W9OqCIgVwV7zeaDP"
Content-Disposition: inline
In-Reply-To: <CAP6exYLd0uFbVSbn28iS1OV=jULtg2f+7t1DAn-fvGoRSd5dng@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--W9OqCIgVwV7zeaDP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 22, 2020 at 01:56:24PM -0700, ron minnich wrote:

> So, let me first add,  the comment can be removed as needed. Comments
> offered only for clarification.

Noted, thanks.

> On Mon, Jun 22, 2020 at 1:40 PM Tom Rini <trini@konsulko.com> wrote:
>=20
> > But what do you mean UEFI "consumes" initrd=3D ?
>=20
> What I mean is, there are bootloaders that will, if they see initrd=3D
> in the command line, remove it: the kernel will never see it.

I'm picky here because, well, there's a whole lot of moving parts in the
pre-kernel world.  In a strict sense, "UEFI" doesn't do anything with
the kernel but based on hpa's comments I assume that at least the
in-kernel UEFI stub does what Documentation/x86/booting.rst suggests to
do and consumes initrd=3D/file just like "initrd /file" in extlinux.conf,
etc do.  And since the EFI stub is cross-platform, it's worth noting
this too.

> >  I guess looking at
> > Documentation/x86/boot.rst is where treating initrd=3D as a file that
> > should be handled and ramdisk_image / ramdisk_size set came from.  I do
> > wonder what happens in the case of ARM/ARM64 + UEFI without device tree.
>=20
> it is possible that the initrd=3D argument will not be seen by the
> kernel. That's my understanding. Will this be a problem if so? It
> would be for me :-)
>=20
> >  And it doesn't provide any sort of link / context to the
> > boot loader specification project or similar that explains the cases
> > when a non-filename "initrd=3D" would reasonably (or unreasonably but
> > happens in reality) be removed.
>=20
> But it unreasonably happens as I learned the hard way :-)
>=20
> Anyway, thanks Tom, I have no objections to whatever you all feel is
> best to do with that comment. It was a failed attempt on my part to
> explain the state of things :-)

Booting up the kernel is quite the "fun" area indeed.

--=20
Tom

--W9OqCIgVwV7zeaDP
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAl7xHDIACgkQFHw5/5Y0
tyykrwwAsipqFRwbV8H3aKv+J9PHEPFRTFClvSda5kTfojpnqbRqpOVQSoHiDYTs
R35RMZZ8DjYl45u0qbmPPEWEw1zP+zxjBosWuZn9/82fMg9QgRg+H6Z8D0VZPfmv
fGSheF8bMhIhEpEJc8yTMW41cEUmm4rotSlULa0eThB7DK8CHxnemQsTvRTv8VJo
5N/djHA0MLmjFclUhlOZ0hFfGSS6MtxBLFZjho8iA5nHbYdQsNj3UxuQ/7AdJiyI
+h0+M/nWEc55vDWL8cJX2Q3o39OFx0ev6iHdUQDHG0RCHSRKY4D+/lIXfxjEQQb5
CtVRIFNeT8cpMghICMcLMPi+ntT3Oel/DbpLovSf5D9SGY1KmWq09tjmuIs98kRT
qNZzc0ehLMBPX0ZpXmyJ5BwtAnO5JfSnuN1I00ufElz7rADa6GH27f15o1QWXv/V
EfM/ueDIEA0nhu1sJY+hAyBX0O1YfFFlDbAGjVjBtSRUDp0LFjMT7Zr+w8Xh7qYq
BEUubv5G
=kliK
-----END PGP SIGNATURE-----

--W9OqCIgVwV7zeaDP--