linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] of/fdt: split off FDT self reservation from memreserve processing
Date: Mon, 1 Jun 2015 10:56:55 +0100	[thread overview]
Message-ID: <20150601095655.GB22406@leverpostej> (raw)
In-Reply-To: <CAKv+Gu8-av3xTTf=YHAmU2TBuQrBWAS4WBLwK9hfgZbX0YH89A@mail.gmail.com>

On Mon, Jun 01, 2015 at 08:56:07AM +0100, Ard Biesheuvel wrote:
> (snip non-LAKML CCs)
> 
> On 22 May 2015 at 12:35, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Mon, May 11, 2015 at 08:41:53AM +0200, Ard Biesheuvel wrote:
> >> This splits off the reservation of the memory occupied by the FDT
> >> binary itself from the processing of the memory reservations it
> >> contains. This is necessary because the physical address of the FDT,
> >> which is needed to perform the reservation, may not be known to the
> >> FDT driver core, i.e., it may be mapped outside the linear direct
> >> mapping, in which case __pa() returns a bogus value.
> >>
> >> Cc: Russell King <linux@arm.linux.org.uk>
> >> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> >> Cc: Paul Mackerras <paulus@samba.org>
> >> Acked-by: Rob Herring <robh@kernel.org>
> >> Acked-by: Mark Rutland <mark.rutland@arm.com>
> >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >
> > For the arm64 part:
> >
> > Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> 
> Thanks Catalin,
> 
> Since there has been virtually no discussion about these patches, I
> guess they have missed the window for being considered for inclusion
> in v4.2
> 
> May I suggest that you at least consider these patches regarding the ID map
> 
> http://article.gmane.org/gmane.linux.ports.arm.kernel/411720
> http://article.gmane.org/gmane.linux.ports.arm.kernel/411721
> 
> since they are self-contained and the first one does fix a potential
> problem where the Image placement logic in the stub does not take the
> 512 MB alignment boundary into account. The second one is a trivial
> cleanup.

FWIW both of these look good to me.

> Perhaps Mark can comment on the desirability to include the FDT
> remapping patch (which depends on this 1/8).
> 
> http://article.gmane.org/gmane.linux.kernel.efi/5738

I would like to see that taken if possible.

Thanks,
Mark.

  reply	other threads:[~2015-06-01  9:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11  6:41 [PATCH 0/8] arm64 UEFI early FDT handling Ard Biesheuvel
2015-05-11  6:41 ` [PATCH 1/8] of/fdt: split off FDT self reservation from memreserve processing Ard Biesheuvel
2015-05-22 10:35   ` Catalin Marinas
2015-06-01  7:56     ` Ard Biesheuvel
2015-06-01  9:56       ` Mark Rutland [this message]
2015-06-01 10:46         ` Ard Biesheuvel
2015-06-01 11:02           ` Mark Rutland
2015-06-01 11:14             ` Ard Biesheuvel
2015-06-01 11:18               ` Mark Rutland
2015-05-11  6:41 ` [PATCH 2/8] arm64: use fixmap region for permanent FDT mapping Ard Biesheuvel
2015-06-01  9:53   ` Mark Rutland
2015-06-01  9:55     ` Ard Biesheuvel
2015-05-11  6:41 ` [PATCH 3/8] arm64: override early_init_dt_add_memory_arch() Ard Biesheuvel
2015-05-11  6:41 ` [PATCH 4/8] efi: move FDT handling to separate object file Ard Biesheuvel
2015-05-26 18:15   ` Matt Fleming
2015-05-11  6:41 ` [PATCH 5/8] arm64/efi: move EFI init before early FDT processing Ard Biesheuvel
2015-05-11  6:41 ` [PATCH 6/8] arm64/efi: ignore DT memory nodes instead of removing them Ard Biesheuvel
2015-05-11 16:28   ` Ganapatrao Kulkarni
2015-05-12 14:31   ` Leif Lindholm
2015-05-12 15:01     ` Ard Biesheuvel
2015-05-11  6:41 ` [PATCH 7/8] arm64/efi: ignore DT memreserve entries " Ard Biesheuvel
2015-05-11  6:42 ` [PATCH 8/8] arm64/efi: adapt to relaxed FDT placement requirements 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=20150601095655.GB22406@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 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).