From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: do not assume DRAM base is aligned to 2 MB
Date: Thu, 29 Oct 2015 15:21:42 +0000 [thread overview]
Message-ID: <20151029152141.GH28221@leverpostej> (raw)
In-Reply-To: <5632347E.2070303@codeaurora.org>
On Thu, Oct 29, 2015 at 10:00:14AM -0500, Timur Tabi wrote:
> On 10/29/2015 09:57 AM, Will Deacon wrote:
> >So is this fixing a regression introduced in 4.3? If so, can I have a
> >Fixes: tag too, please? (I was under the impression that this was a
> >longstanding issue, but the thread hasn't been easy to follow).
>
> It fixes a bug introduced by:
>
> Author: Ard Biesheuvel <ard.biesheuvel@linaro.org> 2015-07-24 06:38:27
> Committer: Will Deacon <will.deacon@arm.com> 2015-07-27 05:08:41
> Parent: ddeeefe2dfbe1fa6b116b9362b1bec465b64c873 (arm64/efi:
> efistub: Apply __init annotation)
> Child: 739fa11938bec53a849b77b2042237a0e17c70ae (arm64/efi: do not
> assume DRAM base is aligned to 2 MB)
> Branches: dcc, master, qserver, qserver2, remotes/origin/master, tty
> Follows: v4.2-rc4
> Precedes: v4.3-rc1
>
> arm64: efi: prefer AllocatePages() over efi_low_alloc() for vmlinux
As it wasn't in the context, that's commit ID e38457c361b30c5a, which
was introduced in v4.3-rc1.
However, the check on the base address was always buggy since its
introduction in v3.16 in commit 3c7f255039a2ad6e ("arm64: efi: add EFI
stub"), so that portion needs to be backported further.
Thanks,
Mark.
next prev parent reply other threads:[~2015-10-29 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 14:07 [PATCH] arm64/efi: do not assume DRAM base is aligned to 2 MB Ard Biesheuvel
2015-10-29 14:52 ` Timur Tabi
2015-10-29 14:57 ` Will Deacon
2015-10-29 15:00 ` Timur Tabi
2015-10-29 15:21 ` Mark Rutland [this message]
2015-10-29 15:23 ` Ard Biesheuvel
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=20151029152141.GH28221@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.