grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
	Colin Watson <cjwatson@debian.org>,
	The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Bugs and tasks for 2.02[~rc1]
Date: Mon, 7 Mar 2016 16:26:18 -0500	[thread overview]
Message-ID: <20160307212617.GG13163@redhat.com> (raw)
In-Reply-To: <56DDEDC6.6080903@gmail.com>

On Tue, Mar 08, 2016 at 12:08:22AM +0300, Andrei Borzenkov wrote:
> 08.03.2016 00:03, Peter Jones пишет:
> 
> > I'm curious as to why you think "linux16" doesn't work for Linux,
> > though.  We use it 100% of the time in Fedora and RHEL, and upstream x86
> > kernel maintainers have expressed a preference for it.  Using "linux"
> > instead seems to break much more, for example EDD often does not ever
> > get exposed to the kernel when it's used.
> > 
> 
> Every now and then I thought about adding EDD to linux loader but as
> nobody actually complained I never felt like doing it. Not sure what it
> is used for as well. How knowing BIOS disk order is useful on Linux?

It's the only way to figure out which disks are okay candidates for
installing the boot loader.  Otherwise you're just rolling the dice.
(Not that EDD is that great, mind you...)

But this speaks to the wider issue of both this and the efi stub: in the
kernel, we're better off getting it directly from the firmware when
possible, rather than have it proxied through grub and a boot params
structure.  That's why the kernel has code to do this in the first
place.

The only thing marshaling it through a pile of structures in memory does
is introduce errors or missing data.  And it adds work coordinating what
goes in those structures.  It's not helpful unless there's a specific
reason to do it.

-- 
  Peter


  reply	other threads:[~2016-03-07 21:26 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 15:01 Bugs and tasks for 2.02[~rc1] Vladimir 'phcoder' Serbinenko
2016-03-02 22:24 ` Daniel Kiper
2016-03-09 10:49   ` Daniel Kiper
     [not found]     ` <20160309144557.GA19753@char.us.oracle.com>
2016-03-09 14:51       ` Vladimir 'phcoder' Serbinenko
2016-03-09 20:05         ` Daniel Kiper
2016-03-04 20:06 ` Peter Jones
2016-03-05  8:38   ` Andrei Borzenkov
2016-03-07 19:00     ` Peter Jones
2016-03-07 19:57       ` Vladimir 'phcoder' Serbinenko
2016-03-07 20:33         ` Andrei Borzenkov
2016-03-07 20:40           ` Vladimir 'phcoder' Serbinenko
2016-03-07 20:57             ` Andrei Borzenkov
2016-03-07 21:03               ` Vladimir 'phcoder' Serbinenko
2016-03-07 21:20               ` Peter Jones
2016-03-07 21:29                 ` Andrei Borzenkov
2016-03-07 22:01                   ` Peter Jones
2016-03-07 22:07                     ` Vladimir 'phcoder' Serbinenko
2016-03-08  4:16                       ` Michael Chang
2016-03-08  3:40                     ` Michael Chang
2016-03-08  4:57                       ` Andrei Borzenkov
2016-03-09 15:18                         ` Matt Fleming
2016-03-09 20:15                           ` Linux loader EFI handover (was: Bugs and tasks for 2.02[~rc1]) Andrei Borzenkov
2016-03-10 14:21                             ` Matt Fleming
2016-03-11 17:46                               ` Linux loader EFI handover Andrei Borzenkov
2016-03-07 21:42                 ` Bugs and tasks for 2.02[~rc1] Matt Fleming
2016-03-11 15:51                   ` Vladimir 'phcoder' Serbinenko
2016-03-14 15:17                     ` Matt Fleming
2016-03-15 17:38                       ` Vladimir 'phcoder' Serbinenko
2016-03-22 17:54                         ` Peter Jones
2016-03-07 21:14             ` Peter Jones
2016-03-07 21:50               ` Vladimir 'phcoder' Serbinenko
2016-03-07 21:10           ` Peter Jones
2016-03-11 18:01             ` Andrei Borzenkov
2016-03-07 21:03         ` Peter Jones
2016-03-07 21:08           ` Andrei Borzenkov
2016-03-07 21:26             ` Peter Jones [this message]
2016-03-07 21:08           ` Vladimir 'phcoder' Serbinenko
2016-03-08 17:57       ` Andrei Borzenkov
2016-03-08 21:47         ` Peter Jones
2016-03-11 18:38           ` Andrei Borzenkov
2016-03-09  6:38 ` Olaf Hering
2016-03-09  7:54   ` Michael Chang
2016-03-09  8:13     ` Andrei Borzenkov
2016-03-11 16:04   ` Vladimir 'phcoder' Serbinenko
2016-04-13  8:49     ` Olaf Hering
2016-03-13  6:30 ` Andrei Borzenkov
2016-03-22 18:48 ` Vladimir 'phcoder' Serbinenko
2016-03-22 19:51   ` Andrei Borzenkov
     [not found]     ` <20160328145903.GF17944@char.us.oracle.com>
2016-04-12 16:44       ` Konrad Rzeszutek Wilk
2016-04-18  4:20       ` Vladimir 'phcoder' Serbinenko
2016-04-18  4:18     ` Vladimir 'phcoder' Serbinenko
2016-04-12 17:53 ` Bruce Dubbs
2016-04-18  4:20   ` Vladimir 'phcoder' Serbinenko
  -- strict thread matches above, loose matches on Subject: below --
2016-03-03 14:47 Juergen Gross
2016-03-09 10:52 ` Daniel Kiper
2016-03-11 15:47   ` Vladimir 'phcoder' Serbinenko
2016-03-11 15:57     ` Juergen Gross

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=20160307212617.GG13163@redhat.com \
    --to=pjones@redhat.com \
    --cc=arvidjaar@gmail.com \
    --cc=cjwatson@debian.org \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.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;
as well as URLs for NNTP newsgroup(s).