From: Daniel Kiper <dkiper@net-space.pl>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Daniel Kiper <dkiper@net-space.pl>,
Juergen Gross <jgross@suse.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
phcoder@gmail.com, Daniel Kiper <daniel.kiper@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Alexander Graf <agraf@suse.de>,
arvidjaar@gmail.com, "Luis R. Rodriguez" <mcgrof@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andy Lutomirski <luto@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>, Amnon Ilan <ailan@redhat.com>,
Thomas Garnier <thgarnie@google.com>,
konrad.wilk@oracle.com
Subject: Re: [RFC PATCH] x86/boot: make ELF kernel multiboot-able
Date: Mon, 20 Feb 2017 19:46:58 +0100 [thread overview]
Message-ID: <20170220184658.GA14469@router-fw-old.local.net-space.pl> (raw)
In-Reply-To: <1eba3218-c770-72e1-dd1c-e5a0f6046acd@zytor.com>
On Thu, Feb 16, 2017 at 09:00:05PM -0800, H. Peter Anvin wrote:
> On 02/16/17 15:27, Daniel Kiper wrote:
> > That is obvious. Do you think that Multiboot/Multiboot2 protocols are
> > substantially suboptimal?
>
> Yes. They push a lot of things into the bootloader for no good reason,
I have not seen anything in Multiboot(2) specs which stipulates that every
bootloader must implement all features. If somebody needs minimal Multiboot(2)
compatible bootloader he/she can do that. Just parse Multiboot(2) header and
provide, let's call it in that way, empty boot data. Is it difficult?
> thus tying the kernel's hands and making the whole boot process more
> fragile.
Every kernel may take from the bootloader via Multiboot(2) what it needs.
No more no less. There is no requirement to use all data provided by
the bootloader.
> It isn't either like Grub has been very good about keeping to any spec,
> their own or others.
Could you be more precise?
Daniel
prev parent reply other threads:[~2017-02-20 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:41 Chao Peng
2017-02-15 16:42 ` Paolo Bonzini
2017-02-16 2:12 ` Chao Peng
2017-02-15 18:12 ` hpa
2017-02-15 20:13 ` Luis R. Rodriguez
2017-02-15 20:58 ` hpa
2017-02-16 2:07 ` Chao Peng
2017-02-16 23:27 ` Daniel Kiper
2017-02-17 5:00 ` H. Peter Anvin
2017-02-20 18:46 ` Daniel Kiper [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=20170220184658.GA14469@router-fw-old.local.net-space.pl \
--to=dkiper@net-space.pl \
--cc=agraf@suse.de \
--cc=ailan@redhat.com \
--cc=arvidjaar@gmail.com \
--cc=bp@suse.de \
--cc=chao.p.peng@linux.intel.com \
--cc=daniel.kiper@oracle.com \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=phcoder@gmail.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®