Searched full:jump (Results 1 – 25 of 41) sorted by relevance
12
| /Documentation/ABI/testing/ |
| D | sysfs-class-chromeos | 22 - "ro": Jump to RO without rebooting.
23 - "rw": Jump to RW without rebooting.
25 - "disable-jump": Disable jump until next reboot.
|
| /Documentation/staging/ |
| D | static-keys.rst | 88 'no-op' in the straight-line codepath with a 'jump' instruction to the
93 This lowlevel patching mechanism is called 'jump label patching', and it gives
180 4) Architecture level code patching interface, 'jump labels'
185 simply fall back to a traditional, load, test, and jump sequence. Also, the
211 5) Static keys / jump label analysis, results (x86_64):
231 The resulting instructions with jump labels generated by GCC is::
251 Without the jump label optimization it looks like::
275 Thus, the disable jump label case adds a 'mov', 'test' and 'jne' instruction
276 vs. the jump label case just has a 'no-op' or 'jmp 0'. (The jmp 0, is patched
277 to a 5 byte atomic no-op instruction at boot-time.) Thus, the disabled jump
[all …]
|
| D | xz.rst | 11 compression ratio even further. E.g. Branch/Call/Jump (BCJ) filters
|
| /Documentation/trace/ |
| D | kprobes.rst | 54 probes work and how jump optimization works. They explain certain
170 How Does Jump Optimization Work?
176 sysctl(8)), Kprobes tries to reduce probe-hit overhead by using a jump
192 - Kprobes verifies that the region that will be replaced by the jump
194 (A jump instruction is multiple bytes, and so may overlay multiple
198 jump into the optimized region. Specifically:
200 - the function contains no indirect jump;
202 the fixup code triggered by the exception could jump back into the
204 - there is no near jump to the optimized region (other than to the first
220 - a jump back to the original execution path.
[all …]
|
| D | tracepoints.rst | 143 with jump labels and avoid conditional branches.
|
| /Documentation/mips/ |
| D | booting.rst | 7 kernel image. Other bootloaders will jump to the ELF start address.
|
| /Documentation/networking/ |
| D | filter.rst | 71 __u8 jt; /* Jump true */
72 __u8 jf; /* Jump false */
77 a code, jt, jf and k value. jt and jf are jump offsets and k a generic
203 encoded. jt and jf are two 8 bit wide jump targets, one for condition
204 "jump if true", the other one "jump if false". Eventually, element k
227 jmp 6 Jump to label
228 ja 6 Jump to label
229 jeq 7, 8, 9, 10 Jump on A == <x>
230 jneq 9, 10 Jump on A != <x>
231 jne 9, 10 Jump on A != <x>
[all …]
|
| D | can_ucan_protocol.rst | 187 data packet, the ``len`` field can be used to jump to the next
257 data packet, the device uses the ``len`` field to jump to the next
|
| /Documentation/features/core/jump-labels/ |
| D | arch-support.txt | 2 # Feature name: jump-labels
|
| /Documentation/sh/ |
| D | register-banks.rst | 33 of the interrupt exception vector jump table offset
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 39 for internal uses, since it can jump backwards due to a leap
142 since the time is allowed to jump under certain conditions.
|
| D | circular-buffers.rst | 52 items are removed. The tail index should never jump the head index, and both
|
| /Documentation/devicetree/bindings/sram/ |
| D | sram.yaml | 251 // value is set at a specific location. If it is then the BROM will jump
266 // cpu0 should jump to SMP entry vector
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 58 into place (arm64 only), and jump to the restart address while at HYP/EL2.
|
| /Documentation/vm/ |
| D | page_owner.rst | 37 not affect to allocation performance, especially if the static keys jump
|
| D | transhuge.rst | 46 for the head page and not the tail page), it should be updated to jump
|
| /Documentation/x86/ |
| D | entry_64.rst | 13 The x86 architecture has quite a few different ways to jump into
|
| D | boot.rst | 196 0200/2 2.00+ jump Jump instruction
342 Field name: jump
348 Contains an x86 jump instruction, 0xEB followed by a signed offset
531 The address to jump to in protected mode. This defaults to the load
910 handover protocol to boot the kernel should jump to this offset.
945 2-byte jump field, which doubles as a length field for the structure, combined
1320 After completing your hook, you should jump to the address
1407 from the boot media and jump to the EFI handover protocol entry point
|
| D | intel_txt.rst | 122 VMEXITs, and then disable VT and jump to the SIPI vector. This
|
| /Documentation/xtensa/ |
| D | mmu.rst | 28 After step 2, we jump to virtual address in the range 0x40000000..0x5fffffff
31 in this code. After step 4, we jump to intended (linked) address of this code.
|
| /Documentation/arm64/ |
| D | booting.rst | 280 - The primary CPU must jump directly to the first instruction of the
298 cpu-release-addr returns a non-zero value, the CPU must jump to this
|
| /Documentation/usb/ |
| D | CREDITS | 19 David E. Nelson <dnelson@jump.net>
|
| /Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 109 this could cause privileged code's indirect branch to jump to a gadget
207 target buffer on indirect jump and jump to gadget code in speculative
287 the kernel to jump to gadget code in the speculative execution paths.
|
| /Documentation/bpf/ |
| D | bpf_devel_QA.rst | 607 lookup and jump operation. Since the switch table is placed
610 The clang option ``-fno-jump-tables`` can be used to disable
630 - You can add ``-fno-jump-tables`` to work around the switch table issue.
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 7 to jump right in and start coding. As with any significant project,
|
12