| /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.
|
| H A D | libbpf_overview.rst | 234 * `API naming convention <https://libbpf.readthedocs.io/en/latest/libbpf_naming_convention.html>`_
236 * `API documentation Convention <https://libbpf.readthedocs.io/en/latest/libbpf_naming_convention.h…
|
| /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
|
| /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
|
| /linux/Documentation/driver-api/cxl/ |
| H A D | conventions.rst | 12 same convention.
39 convention.>
|
| /linux/drivers/firmware/smccc/ |
| H A D | soc_id.c | 18 * As per the SMC Calling Convention specification v1.2 (ARM DEN 0028C)
58 * Issue Number 1.6 of the Arm SMC Calling Convention in smccc_soc_name_init()
71 * Calling Convention, the string will be NUL terminated in smccc_soc_name_init()
|
| /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()
|
| /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?
|
| /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
|
| /linux/drivers/accessibility/speakup/ |
| H A D | i18n.h | 57 MSG_START, /* A little confusing, given our convention. */
58 MSG_END, /* A little confusing, given our convention. */
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | hypercalls.rst | 10 Calling Convention (DEN0028/C):
28 | Calling convention: | HVC32 |
56 | Calling convention: | HVC64 |
80 | Calling convention: | HVC64 |
105 | Calling convention: | HVC64 |
131 | Calling convention: | HVC64 |
154 | Calling convention: | HVC64 |
184 | Calling convention: | HVC64 |
|
| /linux/Documentation/filesystems/ |
| H A 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.
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A 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.
|
| /linux/include/linux/ |
| H A D | compiler_types.h | 119 * On x86-64 and arm64 targets, __preserve_most changes the calling convention
121 * convention behaves identically to the C calling convention on how arguments
131 * does not use __preserve_most or equivalent convention (if in assembly). Since
132 * function tracing assumes the normal C calling convention, where the attribute
|
| /linux/tools/perf/util/ |
| H A D | llvm-c-helpers.cpp | 59 /* Match the convention of libbfd. */ in extract_file_and_line()
109 /* Match the convention of libbfd. */ in llvm_addr2line()
|
| /linux/arch/powerpc/include/uapi/asm/ |
| H A D | tm.h | 6 * convention, bit0 is copied to TEXASR[56] (IBM bit 7) which is set if
|
| /linux/arch/arm64/include/uapi/asm/ |
| H A D | sigcontext.h | 68 * convention due to oversight but it should be observed for future additions.
234 * The same convention applies when returning from a signal: a caller
324 * The same convention applies when returning from a signal: a caller
|
| /linux/Documentation/arch/x86/ |
| H A D | booting-dt.rst | 9 supports one calling convention which is documented in
|
| /linux/arch/mips/include/uapi/asm/ |
| H A D | sgidefs.h | 31 * Subprogram calling convention
|
| /linux/include/uapi/linux/ |
| H A D | atmapi.h | 25 * Convention: NULL pointers are passed as a field of all zeroes.
|
| /linux/arch/mips/kernel/ |
| H A D | scall64-o32.S | 12 * convention than the kernel, so we have to translate things from o32
13 * to ABI64 calling convention. 64-bit syscalls are also processed
|
| /linux/arch/arm64/include/asm/ |
| H A D | asm-prototypes.h | 27 * This function uses a custom calling convention and cannot be called from C so
|
| /linux/arch/x86/include/asm/ |
| H A D | paravirt_types.h | 28 * calling convention. See PV_CALL_SAVE_REGS_THUNK below.
118 * more registers than the standard C calling convention.
272 * convention, in which the first three arguments are placed in %eax,
306 * calling convention can't directly deal with this, so the wrapper
|
| /linux/Documentation/devicetree/bindings/arm/samsung/ |
| H A D | samsung-soc.yaml | 7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
|