Searched refs:jumps (Results 1 – 25 of 28) sorted by relevance
12
| /Linux-v5.4/arch/x86/ |
| D | Makefile_32.cpu | 27 cflags-$(CONFIG_MCRUSOE) += -march=i686 -falign-functions=0 -falign-jumps=0 -falign-loops=0
28 cflags-$(CONFIG_MEFFICEON) += -march=i686 $(call tune,pentium3) -falign-functions=0 -falign-jumps=0…
31 …III) += $(call cc-option,-march=c3,-march=i486) -falign-functions=0 -falign-jumps=0 -falign-loops=0
|
| D | Makefile | 100 KBUILD_CFLAGS += $(call cc-option,-falign-jumps=1)
|
| /Linux-v5.4/drivers/scsi/ |
| D | 53c700.scr | 35 ; necessary amount of data and jumps to the next SG segment. The final
36 ; SG segment jumps back to . However, this address is the first SG script
|
| D | 53c700_d.h_shipped | 38 ; necessary amount of data and jumps to the next SG segment. The final
39 ; SG segment jumps back to . However, this address is the first SG script
|
| /Linux-v5.4/tools/objtool/Documentation/ |
| D | stack-validation.txt | 147 4. Dynamic jumps and jumps to undefined symbols are only allowed if:
155 function's code paths. If a function jumps to code in another file,
|
| /Linux-v5.4/tools/perf/util/ |
| D | annotate.h | 288 u8 jumps; member
|
| D | annotate.c | 2624 notes->widths.jumps = width_jumps(notes->max_jump_sources); in annotation__init_column_widths()
2638 notes->widths.addr += notes->widths.jumps + 1; in annotation__update_column_widths()
2936 notes->widths.jumps, in __annotation_line__write()
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | efi-stub.rst | 9 jumps to are collectively known as the "EFI boot stub", and live in
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | pxa_camera.rst | 149 while the DMA jumps from one Videobuffer to another. On the schema, that
|
| /Linux-v5.4/Documentation/x86/ |
| D | exception-tables.rst | 47 is no vma that contains this address. In this case, the kernel jumps
333 This is legacy case that just jumps to the fixup code
|
| D | intel_txt.rst | 167 - Then the kernel jumps into tboot via the vector specified in the
|
| /Linux-v5.4/tools/bpf/bpftool/Documentation/ |
| D | bpftool-map.rst | 212 programs used for tail-call jumps at runtime, without having to reload the
|
| /Linux-v5.4/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 110 the entry code jumps to the appropriate emulation code within the code section.
|
| D | isp.doc | 119 the entry code jumps to the appropriate emulation code within the code section.
|
| D | TEST.DOC | 105 the entry code jumps to the appropriate test code within the code section.
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | lm90.rst | 392 to use two SMBus transaction for reads, this overhead jumps to +50%. Worse,
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_design_QA.rst | 132 For example why BPF_JNE and other compare and jumps are not cpu-like?
|
| /Linux-v5.4/Documentation/arm64/ |
| D | booting.rst | 98 jumps to code0 to resume the normal boot process.
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 142 the image contents and jumps into a special trampoline area in the original
|
| /Linux-v5.4/arch/sparc/ |
| D | Kconfig | 446 This is the virtual address u-boot jumps to when booting the Linux
|
| /Linux-v5.4/arch/arm64/ |
| D | Kconfig | 1484 Allocate PLTs when loading modules so that jumps and calls whose
1492 region itself may be too far away for ordinary relative jumps and
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 294 Returning from the init function, the MUSB controller driver jumps back
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 442 jumps in the kernel into equivalent return trampolines (retpolines)
|
| /Linux-v5.4/arch/x86/lib/ |
| D | x86-opcode-map.txt | 293 # in "near" jumps and calls is 16-bit. For CALL,
|
| /Linux-v5.4/tools/arch/x86/lib/ |
| D | x86-opcode-map.txt | 293 # in "near" jumps and calls is 16-bit. For CALL,
|
12
