1 Kernel-provided User Helpers
2 ============================
4 These are segment of kernel provided user code reachable from user space
5 at a fixed address in kernel memory. This is used to provide user space
6 with some operations which require kernel help because of unimplemented
7 native feature and/or instructions in many ARM CPUs. The idea is for this
8 code to be executed directly in user mode for best efficiency but which is
9 too intimate with the kernel counter part to be left to user libraries.
10 In fact this code might even differ from one CPU to another depending on
11 the available instruction set, or whether it is a SMP systems. In other
12 words, the kernel reserves the right to change this code as needed without
13 warning. Only the entry points and their results as documented here are
14 guaranteed to be stable.
16 This is different from (but doesn't preclude) a full blown VDSO
17 implementation, however a VDSO would prevent some assembly tricks with
18 constants that allows for efficient branching to those code segments. And
19 since those code segments only use a few cycles before returning to user
20 code, the overhead of a VDSO indirect far call would add a measurable
21 overhead to such minimalistic operations.
23 User space is expected to bypass those helpers and implement those things
24 inline (either in the code emitted directly by the compiler, or part of
25 the implementation of a library call) when optimizing for a recent enough
26 processor that has the necessary native support, but only if resulting
27 binaries are already to be incompatible with earlier ARM processors due to
28 usage of similar native instructions for other things. In other words
29 don't make binaries unable to run on earlier processors just for the sake
30 of not using these kernel helpers if your compiled code is not going to
31 use new instructions for other purpose.
33 New helpers may be added over time, so an older kernel may be missing some
34 helpers present in a newer kernel. For this reason, programs must check
35 the value of __kuser_helper_version (see below) before assuming that it is
36 safe to call any particular helper. This check should ideally be
37 performed only once at process startup time, and execution aborted early
38 if the required helpers are not provided by the kernel version that
39 process is running on.
46 Reference declaration:
48 extern int32_t __kuser_helper_version;
52 This field contains the number of helpers being implemented by the
53 running kernel. User space may read this to determine the availability
54 of a particular helper.
58 #define __kuser_helper_version (*(int32_t *)0xffff0ffc)
60 void check_kuser_version(void)
62 if (__kuser_helper_version < 2) {
63 fprintf(stderr, "can't do atomic operations, kernel too old\n");
70 User space may assume that the value of this field never changes
71 during the lifetime of any single process. This means that this
72 field can be read once during the initialisation of a library or
73 startup phase of a program.
82 void * __kuser_get_tls(void);
98 Get the TLS value as previously set via the __ARM_NR_set_tls syscall.
102 typedef void * (__kuser_get_tls_t)(void);
103 #define __kuser_get_tls (*(__kuser_get_tls_t *)0xffff0fe0)
107 void *tls = __kuser_get_tls();
108 printf("TLS = %p\n", tls);
113 - Valid only if __kuser_helper_version >= 1 (from kernel version 2.6.12).
122 int __kuser_cmpxchg(int32_t oldval, int32_t newval, volatile int32_t *ptr);
133 r0 = success code (zero or non-zero)
134 C flag = set if r0 == 0, clear if r0 != 0
142 Atomically store newval in *ptr only if *ptr is equal to oldval.
143 Return zero if *ptr was changed or non-zero if no exchange happened.
144 The C flag is also set if *ptr was changed to allow for assembly
145 optimization in the calling code.
149 typedef int (__kuser_cmpxchg_t)(int oldval, int newval, volatile int *ptr);
150 #define __kuser_cmpxchg (*(__kuser_cmpxchg_t *)0xffff0fc0)
152 int atomic_add(volatile int *ptr, int val)
159 } while(__kuser_cmpxchg(old, new, ptr));
166 - This routine already includes memory barriers as needed.
168 - Valid only if __kuser_helper_version >= 2 (from kernel version 2.6.12).
177 void __kuser_memory_barrier(void);
193 Apply any needed memory barrier to preserve consistency with data modified
194 manually and __kuser_cmpxchg usage.
198 typedef void (__kuser_dmb_t)(void);
199 #define __kuser_dmb (*(__kuser_dmb_t *)0xffff0fa0)
203 - Valid only if __kuser_helper_version >= 3 (from kernel version 2.6.15).
212 int __kuser_cmpxchg64(const int64_t *oldval,
213 const int64_t *newval,
214 volatile int64_t *ptr);
218 r0 = pointer to oldval
219 r1 = pointer to newval
220 r2 = pointer to target value
225 r0 = success code (zero or non-zero)
226 C flag = set if r0 == 0, clear if r0 != 0
234 Atomically store the 64-bit value pointed by *newval in *ptr only if *ptr
235 is equal to the 64-bit value pointed by *oldval. Return zero if *ptr was
236 changed or non-zero if no exchange happened.
238 The C flag is also set if *ptr was changed to allow for assembly
239 optimization in the calling code.
243 typedef int (__kuser_cmpxchg64_t)(const int64_t *oldval,
244 const int64_t *newval,
245 volatile int64_t *ptr);
246 #define __kuser_cmpxchg64 (*(__kuser_cmpxchg64_t *)0xffff0f60)
248 int64_t atomic_add64(volatile int64_t *ptr, int64_t val)
255 } while(__kuser_cmpxchg64(&old, &new, ptr));
262 - This routine already includes memory barriers as needed.
264 - Due to the length of this sequence, this spans 2 conventional kuser
265 "slots", therefore 0xffff0f80 is not used as a valid entry point.
267 - Valid only if __kuser_helper_version >= 5 (from kernel version 3.1).