From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 00/11] arm64: Unify MMU code v3
Date: Fri, 26 Feb 2016 11:37:42 -0700 [thread overview]
Message-ID: <56D09B76.2070805@wwwdotorg.org> (raw)
In-Reply-To: <1456447761-127289-1-git-send-email-agraf@suse.de>
On 02/25/2016 05:49 PM, Alexander Graf wrote:
> Howdy,
>
> Currently on arm64 there is a big pile of mess when it comes to MMU
> support and page tables. Each board does its own little thing and the
> generic code is pretty dumb and nobody actually uses it.
>
> This patch set tries to clean that up. After this series is applied,
> all boards except for the FSL Layerscape ones are converted to the
> new generic page table logic and have icache+dcache enabled.
>
> The new code always uses 4k page size. It dynamically allocates 1G or
> 2M pages for ranges that fit. When a dcache attribute request comes in
> that requires a smaller granularity than our previous allocation could
> fulfill, pages get automatically split.
>
> I have tested and verified the code works on HiKey (bare metal),
> vexpress64 (Foundation Model) and zynqmp (QEMU). The TX1 target is
> untested, but given the simplicity of the maps I doubt it'll break.
> ThunderX in theory should also work, but I haven't tested it. I would
> be very happy if people with access to those system could give the patch
> set a try.
>
> With this we're a big step closer to a good base line for EFI payload
> support, since we can now just require that all boards always have dcache
> enabled.
>
> I would also be incredibly happy if some Freescale people could look
> at their MMU code and try to unify it into the now cleaned up generic
> code. I don't think we're far off here.
Tested-by: Stephen Warren <swarren@nvidia.com>
(On p2371-0000 and p2371-2180)
prev parent reply other threads:[~2016-02-26 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 0:49 [U-Boot] [PATCH v4 00/11] arm64: Unify MMU code v3 Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 01/11] thunderx: Calculate TCR dynamically Alexander Graf
2016-02-26 2:51 ` Simon Glass
2016-02-26 8:58 ` Alexander Graf
2016-02-26 15:39 ` Simon Glass
2016-02-26 15:44 ` Alexander Graf
2016-02-26 15:50 ` Simon Glass
2016-02-26 0:49 ` [U-Boot] [PATCH v4 02/11] arm64: Disable TTBR1 maps in EL1 Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 03/11] arm64: Make full va map code more dynamic Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 04/11] thunderx: Move mmu table into board file Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 05/11] zymqmp: Replace home grown mmu code with generic table approach Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 06/11] tegra: " Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 07/11] vexpress64: Add MMU tables Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 08/11] dwmmc: Increase retry timeout Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 09/11] hikey: Add MMU tables Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 10/11] arm64: Remove non-full-va map code Alexander Graf
2016-02-26 0:49 ` [U-Boot] [PATCH v4 11/11] arm64: Only allow dcache disabled in SPL builds Alexander Graf
2016-02-26 18:37 ` Stephen Warren [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=56D09B76.2070805@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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