This is the mail archive of the
mailing list for the newlib project.
[ARM] Initializing TTBR0 to inner/outer WB
- From: Jiong Wang <jiong dot wang at foss dot arm dot com>
- To: newlib at sourceware dot org
- Date: Mon, 21 Mar 2016 14:46:52 +0000
- Subject: [ARM] Initializing TTBR0 to inner/outer WB
- Authentication-results: sourceware.org; auth=none
While running tests on internal systems, we identified an issue in the
startup code for newlib on AArch32 systems with Multiprocessor
Extensions to the architecture.
The issue is we were configuring page table flags to be Inner
cacheable/Outer non-cacheable, while for at least architectures with
Multiprocessor Extension, we'd configure it to Inner/Outer write-back, no
write-allocate, and cacheable.
The attached patch fixes this, and no regression on arm-none-eabi
OK for trunk?
2016-03-21 Jiong Wang <firstname.lastname@example.org>
* arm/cpu-init/rdimon-aem.S: Set TTBR0 to inner/outer
cacheable WB, and no allocate on WB for arch with multiprocessor
diff --git a/libgloss/arm/cpu-init/rdimon-aem.S b/libgloss/arm/cpu-init/rdimon-aem.S
index 19814c6..5e9d6d6 100644
@@ -127,7 +127,17 @@ spin:
mcr 15, 0, r4, cr2, cr0, 2 @ Write TTBCR
adr r4, page_table_addr @ Load the base for vectors
ldr r4, [r4]
- add r4, r4, #1 @ Page tables inner cacheable
+ mrc p15, 0, r0, c0, c0, 5 @ read MPIDR
+ ands r0, r0, #0x80000000 @ bis
+ @ Set page table flags - there are two page table flag formats for the
+ @ architecture. For systems without multiprocessor extensions we use 0x1
+ @ which is Inner cacheable/Outer non-cacheable. For systems with
+ @ multiprocessor extensions we use 0x59 which is Inner/Outer write-back,
+ @ no write-allocate, and cacheable. See the ARMARM-v7AR for more details.
+ beq no_mp_extension
+ add r4, r4, #0x58
+ add r4, r4, #1
mcr 15, 0, r4, cr2, cr0, 0 @ Write TTBR0