Skip to content

Commit d50240a

Browse files
wildea01ctmarinas
authored andcommitted
arm64: mm: permit use of tagged pointers at EL0
TCR.TBI0 can be used to cause hardware address translation to ignore the top byte of userspace virtual addresses. Whilst not especially useful in standard C programs, this can be used by JITs to `tag' pointers with various pieces of metadata. This patch enables this bit for AArch64 Linux, and adds a new file to Documentation/arm64/ which describes some potential caveats when using tagged virtual addresses. Signed-off-by: Will Deacon <[email protected]> Signed-off-by: Catalin Marinas <[email protected]>
1 parent 909e3ee commit d50240a

File tree

4 files changed

+37
-1
lines changed

4 files changed

+37
-1
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
Tagged virtual addresses in AArch64 Linux
2+
=========================================
3+
4+
Author: Will Deacon <[email protected]>
5+
Date : 12 June 2013
6+
7+
This document briefly describes the provision of tagged virtual
8+
addresses in the AArch64 translation system and their potential uses
9+
in AArch64 Linux.
10+
11+
The kernel configures the translation tables so that translations made
12+
via TTBR0 (i.e. userspace mappings) have the top byte (bits 63:56) of
13+
the virtual address ignored by the translation hardware. This frees up
14+
this byte for application use, with the following caveats:
15+
16+
(1) The kernel requires that all user addresses passed to EL1
17+
are tagged with tag 0x00. This means that any syscall
18+
parameters containing user virtual addresses *must* have
19+
their top byte cleared before trapping to the kernel.
20+
21+
(2) Tags are not guaranteed to be preserved when delivering
22+
signals. This means that signal handlers in applications
23+
making use of tags cannot rely on the tag information for
24+
user virtual addresses being maintained for fields inside
25+
siginfo_t. One exception to this rule is for signals raised
26+
in response to debug exceptions, where the tag information
27+
will be preserved.
28+
29+
(3) Special care should be taken when using tagged pointers,
30+
since it is likely that C compilers will not hazard two
31+
addresses differing only in the upper bits.
32+
33+
The architecture prevents the use of a tagged PC, so the upper byte will
34+
be set to a sign-extension of bit 55 on exception return.

arch/arm64/include/asm/pgtable-hwdef.h

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -122,5 +122,6 @@
122122
#define TCR_TG1_64K (UL(1) << 30)
123123
#define TCR_IPS_40BIT (UL(2) << 32)
124124
#define TCR_ASID16 (UL(1) << 36)
125+
#define TCR_TBI0 (UL(1) << 37)
125126

126127
#endif

arch/arm64/kernel/entry.S

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -423,6 +423,7 @@ el0_da:
423423
* Data abort handling
424424
*/
425425
mrs x0, far_el1
426+
bic x0, x0, #(0xff << 56)
426427
disable_step x1
427428
isb
428429
enable_dbg

arch/arm64/mm/proc.S

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ ENTRY(__cpu_setup)
147147
* both user and kernel.
148148
*/
149149
ldr x10, =TCR_TxSZ(VA_BITS) | TCR_FLAGS | TCR_IPS_40BIT | \
150-
TCR_ASID16 | (1 << 31)
150+
TCR_ASID16 | TCR_TBI0 | (1 << 31)
151151
#ifdef CONFIG_ARM64_64K_PAGES
152152
orr x10, x10, TCR_TG0_64K
153153
orr x10, x10, TCR_TG1_64K

0 commit comments

Comments
 (0)