arm-trusted-firmware/bl31
Samuel Holland f8578e641b bl31: Split into two separate memory regions
Some platforms are extremely memory constrained and must split BL31
between multiple non-contiguous areas in SRAM. Allow the NOBITS
sections (.bss, stacks, page tables, and coherent memory) to be placed
in a separate region of RAM from the loaded firmware image.

Because the NOBITS region may be at a lower address than the rest of
BL31, __RW_{START,END}__ and __BL31_{START,END}__ cannot include this
region, or el3_entrypoint_common would attempt to invalidate the dcache
for the entire address space. New symbols __NOBITS_{START,END}__ are
added when SEPARATE_NOBITS_REGION is enabled, and the dcached for the
NOBITS region is invalidated separately.

Signed-off-by: Samuel Holland <samuel@sholland.org>
Change-Id: Idedfec5e4dbee77e94f2fdd356e6ae6f4dc79d37
2019-12-29 12:00:40 -06:00
..
aarch64 Merge changes from topic "bs/pmf32" into integration 2019-12-20 10:33:43 +00:00
bl31.ld.S bl31: Split into two separate memory regions 2019-12-29 12:00:40 -06:00
bl31.mk Merge "debugfs: add 9p device interface" into integration 2019-12-20 18:10:50 +00:00
bl31_context_mgmt.c Sanitise includes across codebase 2019-01-04 10:43:17 +00:00
bl31_main.c Refactor ARMv8.3 Pointer Authentication support code 2019-09-13 14:11:59 +01:00
ehf.c Minor changes to documentation and comments 2019-02-28 13:35:21 +00:00
interrupt_mgmt.c Sanitise includes across codebase 2019-01-04 10:43:17 +00:00