Searched full:convention (Results 1 – 25 of 637) sorted by relevance
12345678910>>...26
| /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-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-4.19/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-4.19/include/linux/ |
| D | arm-smccc.h | 20 * This file provides common defines for ARM SMC Calling Convention as
122 * This function is used to make SMC calls following SMC Calling Convention.
140 * Convention. The content of the supplied param are copied to registers 0
286 * This macro is used to make SMC calls following SMC Calling Convention v1.1.
302 * This macro is used to make HVC calls following SMC Calling Convention v1.1.
|
| /kernel/linux/linux-4.19/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-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-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-4.19/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-4.19/arch/x86/boot/compressed/ |
| D | efi_stub_32.S | 20 * In gcc calling convention, EBX, ESP, EBP, ESI and EDI are all callee save.
23 * service functions will comply with gcc calling convention, too.
|
| /kernel/linux/linux-4.19/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-4.19/Documentation/filesystems/ |
| D | adfs.txt | 68 file type information, a file naming convention was devised (initially
71 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /kernel/linux/linux-4.19/arch/x86/platform/efi/ |
| D | efi_stub_32.S | 18 * In gcc calling convention, EBX, ESP, EBP, ESI and EDI are all callee save.
21 * service functions will comply with gcc calling convention, too.
|
| /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-4.19/drivers/staging/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-4.19/Documentation/serial/ |
| D | moxa-smartio | 15 3.3 Device naming convention
102 3.3 Device naming convention
154 3.3 Device naming convention
165 which is named "ttyMxx". For callout port, the naming convention
170 Naming convention for each Smartio/Industio multiport board is
394 convention, all you have to do is to modify the internal code
|
| /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-4.19/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-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-4.19/arch/powerpc/include/uapi/asm/ |
| D | tm.h | 6 * convention, bit0 is copied to TEXASR[56] (IBM bit 7) which is set if
|
| /kernel/linux/linux-5.10/arch/powerpc/include/uapi/asm/ |
| D | tm.h | 6 * convention, bit0 is copied to TEXASR[56] (IBM bit 7) which is set if
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | booting-dt.rst | 9 supports one calling convention which is documented in
|
12345678910>>...26