From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Kiper <dkiper@net-space.pl>,
The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Juergen Gross <jgross@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Daniel Kiper <daniel.kiper@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Alexander Graf <agraf@suse.de>, Ingo Molnar <mingo@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andy Lutomirski <luto@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>, Amnon Ilan <ailan@redhat.com>,
Thomas Garnier <thgarnie@google.com>,
phcoder@gmail.com, arvidjaar@gmail.com, konrad.wilk@oracle.com
Subject: Re: [RFC PATCH] x86/boot: make ELF kernel multiboot-able
Date: Thu, 16 Feb 2017 21:00:05 -0800 [thread overview]
Message-ID: <1eba3218-c770-72e1-dd1c-e5a0f6046acd@zytor.com> (raw)
In-Reply-To: <20170216232727.GB31716@router-fw-old.local.net-space.pl>
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,
thus tying the kernel's hands and making the whole boot process more
fragile.
It isn't either like Grub has been very good about keeping to any spec,
their own or others.
-hpa
next prev parent reply other threads:[~2017-02-17 5:01 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 [this message]
2017-02-20 18:46 ` Daniel Kiper
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=1eba3218-c770-72e1-dd1c-e5a0f6046acd@zytor.com \
--to=hpa@zytor.com \
--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=dkiper@net-space.pl \
--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®