grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Michel Hermier <michel.hermier@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: yanjianlong <yanjianlong@huawei.com>
Subject: Re: Grub2: add UEFI support for accessing memory address above 4GB.
Date: Tue, 7 Mar 2017 18:08:48 +0100	[thread overview]
Message-ID: <CAAZ5spBiKUPXq1nQRW4nXi8AK-vVdE7fvpr0HethfGRm2ByeCg@mail.gmail.com> (raw)
In-Reply-To: <CAEaD8JN9Dw=fyu+DiHytv+Z_BZApdox9B7YiKKvZAEKdTCHnfA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]

Le 7 mars 2017 17:24, "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com> a
écrit :



On Tue, Mar 7, 2017, 08:15 Leif Lindholm <leif.lindholm@linaro.org> wrote:

> On Tue, Mar 07, 2017 at 01:55:01AM +0000, Yufuping wrote:
> > Who can add the new feature for grub2:
> > Add UEFI support for accessing memory address above 4GB.
>
> Presumably you mean for x86_64?
> Since GRUB supports all 5 architectures currently supported by the
> UEFI specification, 3 of which are 64-bit, it is useful to be a bit
> more precise.
>
> > When using grub2 as PXE downloading engine, grub2 can get initrd
> > file from network and put it to memory above 4GB.
>
I'd like to know more about the usecase. Generally you should avoid
downloading or loading too large files in bootloader. I.a. TFTP protocol
has problems with files over about 100MIB. Generally you should download
only kernel + initrd and rest of the system should be on iSCSI or NFS.

>
> I can think of nothing particularly related to PXE here.
> The x86_64 port currently sets GRUB_EFI_MAX_USABLE_ADDRESS to
> 0xffffffff or 0x7fffffff, depending on toolchain configuration.
>
> ARM64 sets it to 0xffffffffffffULL, and that works fine.
>
> I seem to recall that the x86_64 port was being restricted due to
> known bad firmware encountered in the past. It could be that it would
> be worth adding an option to configure for enabling access to higher
> addresses, alternatively for retaining compatibility with the broken
> systems.
>
I'm opposed to a config option for this. We don't want to have several
variants of grub binaries for the same platform. If we want to support
>4GiB memory we should detect the buggy firmware on runtime. It's pretty
easy: buggy firmware didn't map memory above 4GiB. We can then either avoid
memory above 4GiB or map it ourselves.


What about a dynamic variable instead or at least accessible from script?
So a user could redefine a value of any kind.


> > The feature should support UEFI BIOS boot mode.
>
> I do not understand this statement.
>
> /
>     Leif
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

[-- Attachment #2: Type: text/html, Size: 5484 bytes --]

  reply	other threads:[~2017-03-07 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E2038AA59DBA7C47A3E5F307432A734C3180A89E@DGGEMA505-MBS.china.huawei.com>
2017-03-07  1:55 ` Grub2: add UEFI support for accessing memory address above 4GB Yufuping
2017-03-07 15:58   ` Leif Lindholm
2017-03-07 16:23     ` Vladimir 'phcoder' Serbinenko
2017-03-07 17:08       ` Michel Hermier [this message]
2017-03-07 17:22         ` Vladimir 'phcoder' Serbinenko
2017-03-07 18:13           ` Michel Hermier
2017-03-07 18:20             ` Vladimir 'phcoder' Serbinenko
2017-03-08  9:57               ` Brendan Trotter
2017-03-08 11:46                 ` Michel Hermier

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=CAAZ5spBiKUPXq1nQRW4nXi8AK-vVdE7fvpr0HethfGRm2ByeCg@mail.gmail.com \
    --to=michel.hermier@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=yanjianlong@huawei.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).