mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Harald Hoyer <harald@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH V2] efi_high_alloc: use EFI_ALLOCATE_MAX_ADDRESS
Date: Wed, 27 Aug 2014 11:30:38 +0100	[thread overview]
Message-ID: <20140827103038.GB28116@console-pimps.org> (raw)
In-Reply-To: <53FB4952.1090104@redhat.com>

On Mon, 25 Aug, at 04:33:54PM, Harald Hoyer wrote:
> 
> So is that ok, if other callers of efi_high_alloc() get an address >
> 4GB?

Yeah, the issue at hand is that some x86 EFI firmware cannot perform a
file read into a buffer above 4G. The actual allocation works fine.

If other callers want a high address buffer, they're not going to hit
that issue. We've no reason to believe that this bug affects arm64 at
all, for instance.

Working around this problem in efi_high_alloc() gives the impression
that there's something wrong with AllocatePages(), which isn't the case.

> Will the buggy EFI implementation work with the usage of the other
> caller's allocated memory? Or will they run into the same issues as
> the initramfs loader?

Based on the information we've gathered so far, there's no reason to
believe other callers will hit the same issue as the file reading code.

-- 
Matt Fleming, Intel Open Source Technology Center

      reply	other threads:[~2014-08-27 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 13:48 [PATCH] " harald
2014-08-25 10:34 ` Matt Fleming
2014-08-25 11:10   ` Harald Hoyer
2014-08-25 11:55 ` [PATCH V2] " harald
2014-08-25 13:07   ` Matt Fleming
2014-08-25 14:33     ` Harald Hoyer
2014-08-27 10:30       ` Matt Fleming [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=20140827103038.GB28116@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=harald@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.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®