From: Shea Levy <shea@shealevy.com>
To: linux-kernel@vger.kernel.org
Cc: matt.fleming@intel.com, "H. Peter Anvin" <hpa@zytor.com>
Subject: Proposal: EFI boot stub configuration file
Date: Fri, 16 Mar 2012 17:25:41 -0400 [thread overview]
Message-ID: <4F63AFD5.3010607@shealevy.com> (raw)
Hello,
In some EFI boot environments (e.g. booting from an external medium or
non-standard systems where tools like efibootmgr don't work), it is
currently impossible to pass the right arguments to the kernel unless an
EFI shell is launched. To ameliorate this, I propose that if
image->load_options_size is 0 (indicating no arguments were passed) AND
image->parent_handle is NULL (indicating that the image was loaded
automatically by the firmware), then the kernel looks for a file in some
fixed, possibly configurable place (e.g. \efi\linux\params), sets
image->load_options_size to its size, and sets image->load_options to
its contents. On any error whatsoever (finding the file, reading it,
getting its size, whatever), any allocated memory would be freed and
load_options_size would be set back to 0. Since the arguments are
already converted to ASCII and parsed during the boot process, the file
would be expected to be in UCS-2 format and no validation would be done
in the configuration loading code. I'll write something up over the next
week or so and submit it as an RFC patch series, but I thought I'd post
this here first in case anyone has immediate feedback based on this
description.
Cheers,
Shea Levy
next reply other threads:[~2012-03-16 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:25 Shea Levy [this message]
2012-03-16 21:28 ` Proposal: EFI boot stub configuration file H. Peter Anvin
2012-03-16 21:36 ` Shea Levy
2012-03-16 21:32 ` Shea Levy
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=4F63AFD5.3010607@shealevy.com \
--to=shea@shealevy.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox