From: hpa@zytor.com
To: Matthew Garrett <mjg59@google.com>
Cc: ron minnich <rminnich@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE..." <x86@kernel.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] x86 support for the initrd= command line option
Date: Mon, 23 Mar 2020 11:19:21 -0700 [thread overview]
Message-ID: <A814A71D-0450-4724-885B-859BCD2B7CBD@zytor.com> (raw)
In-Reply-To: <CACdnJusmAHJYauKvHEXNZKaUWPqZoabB_pSn5WokSy_gOnRtTw@mail.gmail.com>
On March 20, 2020 11:19:19 AM PDT, Matthew Garrett <mjg59@google.com> wrote:
>On Thu, Mar 19, 2020 at 5:59 PM <hpa@zytor.com> wrote:
>
>> It has been designated consumed by the bootloader on x86 since at
>least 1995. So ARM broke it.
>
>Eh. This feels like a matter of semantics - booting the kernel via EFI
>results in it being parsed by the boot stub, so in that case we're
>left arguing that the boot stub isn't the kernel. I can just about buy
>that, but it's a stretch. For this change to actually break something,
>we'd need the bootloader to be passing something that the kernel
>parses, but not actually populating the initrd fields in bootparams.
>That seems unlikely?
You are right as long as this is the very last priority *and* neither boot loaders nor the kernel will croak on unexpected input (I really object to Ron calling the non-x86 version "standard", but that's a whole other ball of wax.)
Pointing to any number of memory chunks via setup_data works and doesn't need to be exposed to the user, but I guess the above is reasonable.
*However*, I would also suggest adding "initrdmem=" across architectures that doesn't have the ambiguity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-03-23 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 23:49 [PATCH 1/1] x86 support for the initrd= command line option ron minnich
2020-03-19 23:57 ` hpa
2020-03-20 0:50 ` ron minnich
2020-03-20 0:59 ` hpa
2020-03-20 15:39 ` ron minnich
2020-03-20 18:19 ` Matthew Garrett
2020-03-23 18:19 ` hpa [this message]
2020-03-23 18:54 ` ron minnich
2020-03-23 19:05 ` hpa
2020-03-23 19:40 ` ron minnich
2020-03-23 21:41 ` hpa
2020-03-23 22:29 ` ron minnich
2020-03-23 22:38 ` ron minnich
2020-03-24 16:05 ` ron minnich
2020-03-24 16:12 ` Randy Dunlap
2020-03-24 16:19 ` ron minnich
2020-03-25 17:21 ` hpa
2020-04-27 7:35 ` [tip: x86/boot] x86/setup: Add an initrdmem= option to specify initrd physical address tip-bot2 for Ronald G. Minnich
2020-03-25 3:30 ` [PATCH 1/1] x86 support for the initrd= command line option H. Peter Anvin
2020-03-25 16:19 ` ron minnich
2020-03-25 17:20 ` hpa
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=A814A71D-0450-4724-885B-859BCD2B7CBD@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@google.com \
--cc=rminnich@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.