Searched full:convention (Results 1 – 25 of 720) sorted by relevance
12345678910>>...29
| /kernel/linux/linux-6.6/Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 3 API naming convention
7 functions and types. Every group has its own naming convention
68 API documentation above. See API naming convention to choose the right
145 API documentation convention
151 convention in which these comments should be formatted.
|
| /kernel/linux/linux-5.10/Documentation/mips/ |
| D | booting.rst | 23 Legacy bootloaders do not use this convention, and they do not pass in a
27 This convention is defined for 32-bit systems only, as there are not
|
| /kernel/linux/linux-6.6/Documentation/arch/mips/ |
| D | booting.rst | 23 Legacy bootloaders do not use this convention, and they do not pass in a
27 This convention is defined for 32-bit systems only, as there are not
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | arm-smccc.h | 13 * This file provides common defines for ARM SMC Calling Convention as
290 * This function is used to make HVC calls following SMC Calling Convention
304 * This function is used to make SMC calls following SMC Calling Convention
333 * This function is used to make SMC calls following SMC Calling Convention.
361 * Convention. The content of the supplied param are copied to registers 0
482 * This macro is used to make SMC calls following SMC Calling Convention v1.1.
498 * This macro is used to make HVC calls following SMC Calling Convention v1.1.
|
| D | compiler_types.h | 110 * On x86-64 and arm64 targets, __preserve_most changes the calling convention
112 * convention behaves identically to the C calling convention on how arguments
122 * does not use __preserve_most or equivalent convention (if in assembly). Since
123 * function tracing assumes the normal C calling convention, where the attribute
|
| /kernel/linux/linux-6.6/Documentation/bpf/standardization/ |
| D | abi.rst | 11 Registers and calling convention
17 The BPF calling convention is defined as:
|
| /kernel/linux/linux-5.10/arch/arm/xen/ |
| D | hypercall.S | 34 * The Xen hypercall calling convention is very similar to the ARM
35 * procedure calling convention: the first paramter is passed in r0, the
38 * in r4, differently from the procedure calling convention of using the
|
| /kernel/linux/linux-6.6/arch/arm/xen/ |
| D | hypercall.S | 34 * The Xen hypercall calling convention is very similar to the ARM
35 * procedure calling convention: the first paramter is passed in r0, the
38 * in r4, differently from the procedure calling convention of using the
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | README.rst | 3 libbpf API naming convention
7 functions and types. Every group has its own naming convention
85 API documentation above. See API naming convention to choose the right
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | bpf_design_QA.rst | 26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen?
36 defines calling convention that is compatible with C calling
37 convention of the linux kernel on those architectures.
45 A: NO. BPF calling convention only allows registers R1-R5 to be used
62 Q: Does C-calling convention diminishes possible use cases?
|
| /kernel/linux/linux-6.6/arch/xtensa/include/uapi/asm/ |
| D | swab.h | 47 * __asm__ macro follows convention that the upper 16 bits of an in __arch_swab16()
49 * follow convention; indeed, it leaves garbage in the upport 16 in __arch_swab16()
|
| /kernel/linux/linux-5.10/arch/xtensa/include/uapi/asm/ |
| D | swab.h | 47 * __asm__ macro follows convention that the upper 16 bits of an in __arch_swab16()
49 * follow convention; indeed, it leaves garbage in the upport 16 in __arch_swab16()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | arm-smccc.h | 12 * This file provides common defines for ARM SMC Calling Convention as
182 * This function is used to make SMC calls following SMC Calling Convention.
200 * Convention. The content of the supplied param are copied to registers 0
331 * This macro is used to make SMC calls following SMC Calling Convention v1.1.
347 * This macro is used to make HVC calls following SMC Calling Convention v1.1.
|
| /kernel/linux/linux-6.6/arch/ia64/kernel/ |
| D | pal.S | 43 * uses the static calling convention, i.e., the RSE may not be used and
52 * Make a PAL call using the static calling convention.
95 * Make a PAL call using the stacked registers calling convention.
131 * Make a physical mode PAL call using the static registers calling convention.
|
| /kernel/linux/linux-5.10/arch/ia64/kernel/ |
| D | pal.S | 43 * uses the static calling convention, i.e., the RSE may not be used and
52 * Make a PAL call using the static calling convention.
95 * Make a PAL call using the stacked registers calling convention.
131 * Make a physical mode PAL call using the static registers calling convention.
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | classic_vs_extended.rst | 24 etc, and eBPF calling convention maps directly to ABIs used by the kernel on
61 - Introduces bpf_call insn and register passing convention for zero overhead
66 convention, then the interpreter will take them from registers and pass
71 instruction. This calling convention was picked to cover common call
189 them across the calls as defined by calling convention.
|
| D | bpf_design_QA.rst | 26 BPF is generic instruction set *with* C calling convention.
29 Q: Why C calling convention was chosen?
36 defines calling convention that is compatible with C calling
37 convention of the linux kernel on those architectures.
45 A: NO. BPF calling convention only allows registers R1-R5 to be used
62 Q: Does C-calling convention diminishes possible use cases?
|
| /kernel/linux/linux-6.6/Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 14 3.2 Device naming convention
105 3.2 Device naming convention
113 Naming convention for each Smartio/Industio multiport board is
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | i18n.h | 51 MSG_START, /* A little confusing, given our convention. */
52 MSG_END, /* A little confusing, given our convention. */
|
| /kernel/linux/linux-6.6/drivers/accessibility/speakup/ |
| D | i18n.h | 57 MSG_START, /* A little confusing, given our convention. */
58 MSG_END, /* A little confusing, given our convention. */
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | adfs.rst | 101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | adfs.rst | 101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /kernel/linux/linux-5.10/kernel/kcsan/ |
| D | atomic.h | 10 * common, however, the current convention is to not mark them; returns true if
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 31 It is *strongly* recommended that 5200B device trees follow this convention
39 "fsl,mpc5200-psc-i2s", not "fsl,mpc5200-i2s". This convention is chosen to
51 convention for SOC devices.
|
| /kernel/linux/linux-6.6/arch/arm64/include/uapi/asm/ |
| D | sigcontext.h | 68 * convention due to oversight but it should be observed for future additions.
210 * The same convention applies when returning from a signal: a caller
300 * The same convention applies when returning from a signal: a caller
|
12345678910>>...29