Lines Matching refs:in

8 * Isolate your NEON code in a separate compilation unit, and compile it with
12 * Don't sleep in your NEON code, and be aware that it will be executed with
18 It is possible to use NEON instructions (and in some cases, VFP instructions) in
19 code that runs in kernel mode. However, for performance reasons, the NEON/VFP
23 may call schedule()], as NEON or VFP instructions will be executed in a
32 contending for the NEON/VFP unit (or, in the SMP case, when a task migrates to
34 every context switch, resulting in a trap when subsequently a NEON/VFP
35 instruction is issued, allowing the kernel to step in and perform the restore if
38 Any use of the NEON/VFP unit in kernel mode should not interfere with this, so
48 Interruptions in kernel mode
54 following rules and restrictions apply in the kernel:
55 * NEON/VFP code is not allowed in interrupt context;
60 kernel_neon_end() and kernel_neon_begin() in places in your code where none of
62 reasonably cheap if no context switch occurred in the meantime)
71 current instruction and arguments, and emulates the instruction in software.
74 executed in kernel mode. If such a condition is encountered, the kernel will
84 kernel is currently compiled at -O2, future changes may result in NEON/VFP
85 instructions appearing in unexpected places if no special care is taken.
87 Therefore, the recommended and only supported way of using NEON/VFP in the
89 * isolate the NEON code in a separate compilation unit and compile it with
96 both NEON and VFP instructions will only ever appear in designated compilation
117 observe the following in addition to the rules above: