From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: Shea Levy <shea-yfkUTty7RcRWk0Htik3J/w@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Revisiting EFI boot stub config file support
Date: Tue, 01 Jan 2013 09:24:04 -0800 [thread overview]
Message-ID: <50E31BB4.7040702@zytor.com> (raw)
In-Reply-To: <50E306FB.6080607-yfkUTty7RcRWk0Htik3J/w@public.gmane.org>
On 01/01/2013 07:55 AM, Shea Levy wrote:
> Hi all,
>
> In March last year, I submitted a patch to enable the EFI boot stub to
> read its config arguments from a file on the ESP, both to help with
> booting from livecds and to avoid having to use efibootmgr every time
> you change your boottime arguments. I ended up dropping the submission
> because I ended up coming to the conclusion that tools like rEFInd and
> gummiboot were better suited to the task of boot managing than the
> kernel itself.
>
> Since then, however, I've received enough emails asking about the status
> of the patch that I think there is room for a simpler entrant into the
> field of linux EFI boot management. This could be in-kernel, as per my
> original patch, or a very simple out-of-kernel (but maybe distributed
> in-tree?) efi image that simply reads linux.conf and boots linux with
> those parameters. My personal bias is still toward handling this
> functionality outside of the kernel itself, but before I started the
> work I thought I'd ask here if anyone thought I should instead bring my
> old patch up-to-date.
>
I am willing to accept this (but I am not the first-line maintainer,
Matt is) in the kernel EFI stub as long as there are no hard-coded
filenames involved, no automatic behavior, and no "scanning". Those are
showstoppers, as is adding to the boot time for nonusers.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Shea Levy <shea@shealevy.com>
Cc: linux-efi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Revisiting EFI boot stub config file support
Date: Tue, 01 Jan 2013 09:24:04 -0800 [thread overview]
Message-ID: <50E31BB4.7040702@zytor.com> (raw)
In-Reply-To: <50E306FB.6080607@shealevy.com>
On 01/01/2013 07:55 AM, Shea Levy wrote:
> Hi all,
>
> In March last year, I submitted a patch to enable the EFI boot stub to
> read its config arguments from a file on the ESP, both to help with
> booting from livecds and to avoid having to use efibootmgr every time
> you change your boottime arguments. I ended up dropping the submission
> because I ended up coming to the conclusion that tools like rEFInd and
> gummiboot were better suited to the task of boot managing than the
> kernel itself.
>
> Since then, however, I've received enough emails asking about the status
> of the patch that I think there is room for a simpler entrant into the
> field of linux EFI boot management. This could be in-kernel, as per my
> original patch, or a very simple out-of-kernel (but maybe distributed
> in-tree?) efi image that simply reads linux.conf and boots linux with
> those parameters. My personal bias is still toward handling this
> functionality outside of the kernel itself, but before I started the
> work I thought I'd ask here if anyone thought I should instead bring my
> old patch up-to-date.
>
I am willing to accept this (but I am not the first-line maintainer,
Matt is) in the kernel EFI stub as long as there are no hard-coded
filenames involved, no automatic behavior, and no "scanning". Those are
showstoppers, as is adding to the boot time for nonusers.
-hpa
next prev parent reply other threads:[~2013-01-01 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 15:55 Revisiting EFI boot stub config file support Shea Levy
[not found] ` <50E306FB.6080607-yfkUTty7RcRWk0Htik3J/w@public.gmane.org>
2013-01-01 17:24 ` H. Peter Anvin [this message]
2013-01-01 17:24 ` H. Peter Anvin
[not found] ` <50E31BB4.7040702-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-01-02 13:26 ` Shea Levy
2013-01-02 13:26 ` Shea Levy
[not found] ` <710F73BE-9F65-48C9-8739-BFCF097F4B07-yfkUTty7RcRWk0Htik3J/w@public.gmane.org>
2013-01-02 17:43 ` Matthew Garrett
2013-01-02 17:43 ` Matthew Garrett
[not found] ` <20130102174319.GA2590-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-01-02 17:52 ` Shea Levy
2013-01-02 17:52 ` Shea Levy
[not found] ` <4DA0AD0B-49D1-4938-B38D-A15C378167B0-yfkUTty7RcRWk0Htik3J/w@public.gmane.org>
2013-01-02 17:54 ` Matthew Garrett
2013-01-02 17:54 ` Matthew Garrett
2013-01-02 17:52 ` H. Peter Anvin
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=50E31BB4.7040702@zytor.com \
--to=hpa-ymnouzjc4hwavxtiumwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shea-yfkUTty7RcRWk0Htik3J/w@public.gmane.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.