| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A 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.
|
| /openbmc/linux/Documentation/arch/mips/ |
| H A 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
|
| /openbmc/u-boot/include/linux/ |
| H A D | arm-smccc.h | 9 * This file provides common defines for ARM SMC Calling Convention as
88 * This function is used to make SMC calls following SMC Calling Convention.
106 * Convention. The content of the supplied param are copied to registers 0
|
| /openbmc/linux/Documentation/bpf/standardization/ |
| H A D | abi.rst | 11 Registers and calling convention
17 The BPF calling convention is defined as:
|
| /openbmc/linux/include/linux/ |
| H A 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.
|
| H A 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
|
| /openbmc/linux/arch/arm/xen/ |
| H A 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
|
| /openbmc/qemu/common-user/host/mips/ |
| H A D | safe-syscall.inc.S | 27 * convention here is that of a C varargs function with the
52 * The syscall calling convention is nearly the same as C:
79 * The syscall calling convention is nearly the same as C:
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libsmi/libsmi/ |
| H A D | libsmi-fix-the-test-dump-files.patch | 108 + import SNMPv2-TC (TEXTUAL-CONVENTION, DisplayString,
132 "This textual convention is an extension of the
133 InterfaceIndex convention. The latter defines a greater
155 + TEXTUAL-CONVENTION);
194 + import SNMPv2-TC (TEXTUAL-CONVENTION, RowStatus,
|
| /openbmc/linux/arch/xtensa/include/uapi/asm/ |
| H A 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()
|
| /openbmc/u-boot/arch/xtensa/include/asm/ |
| H A D | byteorder.h | 42 * __asm__ macro follows convention that the upper 16 bits of an in ___arch__swab16()
44 * follow convention; indeed, it leaves garbage in the upport 16 in ___arch__swab16()
|
| /openbmc/qemu/common-user/host/riscv/ |
| H A D | safe-syscall.inc.S | 22 * convention here is that of a C varargs function with the
30 * The syscall calling convention is nearly the same as C:
|
| /openbmc/qemu/common-user/host/aarch64/ |
| H A D | safe-syscall.inc.S | 21 * convention here is that of a C varargs function with the
28 /* The syscall calling convention isn't the same as the
|
| /openbmc/linux/arch/ia64/kernel/ |
| H A 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.
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | gadget_chips.h | 153 * usb_gadget_controller_number - support bcdDevice id convention
159 * NOTE: this convention is purely optional, and has no meaning in terms of
160 * any USB specification. If you want to use a different convention in your
|
| /openbmc/qemu/common-user/host/loongarch64/ |
| H A D | safe-syscall.inc.S | 25 * convention here is that of a C varargs function with the
33 * The syscall calling convention is nearly the same as C:
|
| /openbmc/qemu/common-user/host/sparc64/ |
| H A D | safe-syscall.inc.S | 32 * convention here is that of a C varargs function with the
40 * The syscall calling convention isn't the same as the C one:
|
| /openbmc/qemu/common-user/host/x86_64/ |
| H A D | safe-syscall.inc.S | 18 * convention here is that of a C varargs function with the
36 * The syscall calling convention isn't the same as the C one:
|
| /openbmc/qemu/common-user/host/arm/ |
| H A D | safe-syscall.inc.S | 26 * convention here is that of a C varargs function with the
45 /* The syscall calling convention isn't the same as the C one:
|
| /openbmc/qemu/common-user/host/s390x/ |
| H A D | safe-syscall.inc.S | 19 * convention here is that of a C varargs function with the
45 * The syscall calling convention isn't the same as the C one:
|
| /openbmc/linux/Documentation/bpf/ |
| H A 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.
|
| H A 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?
|
| /openbmc/docs/designs/ |
| H A D | device-tree-gpio-naming.md | 37 - Ensure common function GPIOs within OpenBMC use the same naming convention
42 naming convention and then the sub bullets list the common GPIO names to be used
43 (when available on an OpenBMC system). This naming convention must be followed
|
| /openbmc/qemu/common-user/host/i386/ |
| H A D | safe-syscall.inc.S | 19 * convention here is that of a C varargs function with the
39 /* The syscall calling convention isn't the same as the C one:
|
| /openbmc/linux/Documentation/driver-api/tty/ |
| H A 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
|