| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | tagged-address-abi.rst | 2 AArch64 TAGGED ADDRESS ABI
11 ABI on AArch64 Linux.
19 syscall ABI that allows userspace to pass certain tagged pointers to
22 2. AArch64 Tagged Address ABI
72 Address ABI for the calling thread.
83 Address ABI for the calling thread.
95 When the AArch64 Tagged Address ABI is enabled for a thread, the
112 3. AArch64 Tagged Address ABI Exceptions
116 ABI relaxation:
157 /* check/enable the tagged address ABI */
[all …]
|
| /openbmc/openbmc/poky/meta/conf/machine/include/x86/ |
| H A D | arch-x86.inc | 12 # ELF32 ABI
13 TUNEVALID[m32] = "IA32 ELF32 standard ABI"
19 # x32 ABI
20 TUNEVALID[mx32] = "IA32e (x86_64) ELF32 standard ABI"
31 # ELF64 ABI
32 TUNEVALID[m64] = "IA32e (x86_64) ELF64 standard ABI"
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
| H A D | 0019-Re-introduce-spe-commandline-options.patch | 24 +; PPC SPE ABI
31 +Use the SPE ABI extensions.
35 +Do not use the SPE ABI extensions.
37 ; Altivec ABI
|
| /openbmc/u-boot/arch/riscv/ |
| H A D | Makefile | 8 ABI = lp64 macro
12 ABI = ilp32 macro
27 ARCH_FLAGS = -march=$(ARCH_BASE)$(ARCH_A)$(ARCH_C) -mabi=$(ABI) \
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc/ |
| H A D | kexec-x32.patch | 4 Subject: [PATCH] x86_64: Add support to build kexec-tools with x32 ABI
11 configure.ac: Add test for detect x32 ABI.
13 x32 ABI is set.
14 kexec/arch/x86_64/kexec-elf-rel-x86_64.c: When x32 ABI is set
16 kexec/kexec-syscall.h: Add correct syscall number for x32 ABI.
39 + dnl ---Test for x32 ABI in x86_64
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-removed.rst | 1 ABI removed symbols
4 .. kernel-abi:: ABI/removed
|
| H A D | abi-obsolete.rst | 1 ABI obsolete symbols
10 .. kernel-abi:: ABI/obsolete
|
| H A D | abi-stable.rst | 1 ABI stable symbols
13 .. kernel-abi:: ABI/stable
|
| H A D | abi-testing.rst | 1 ABI testing symbols
19 .. kernel-abi:: ABI/testing
|
| /openbmc/linux/Documentation/ |
| H A D | Kconfig | 16 bool "Warn if there are errors at ABI files"
18 The files under Documentation/ABI should follow what's
19 described at Documentation/ABI/README. Yet, as they're manually
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /openbmc/qemu/docs/user/ |
| H A D | main.rst | 148 * ``qemu-mips`` executes 32-bit big endian MIPS binaries (MIPS O32 ABI).
150 * ``qemu-mipsel`` executes 32-bit little endian MIPS binaries (MIPS O32 ABI).
152 * ``qemu-mips64`` executes 64-bit big endian MIPS binaries (MIPS N64 ABI).
155 ABI).
157 * ``qemu-mipsn32`` executes 32-bit big endian MIPS binaries (MIPS N32 ABI).
160 ABI).
174 * ``qemu-sparc`` can execute Sparc32 binaries (Sparc32 CPU, 32 bit ABI).
177 (Sparc64 CPU, 32 bit ABI).
179 * ``qemu-sparc64`` can execute some Sparc64 (Sparc64 CPU, 64 bit ABI) and
180 SPARC32PLUS binaries (Sparc64 CPU, 32 bit ABI).
|
| /openbmc/linux/Documentation/translations/zh_CN/userspace-api/ |
| H A D | sysfs-platform_profile.rst | 32 sysfs-platform_profile ABI 文档定义了一个固定的配置文件名集合。驱动程序
40 sysfs-platform_profile ABI文档中。
|
| /openbmc/openbmc/poky/meta/conf/machine/include/mips/ |
| H A D | README | 10 *) o32, n32, n64 ABI
43 that the tune is using a non-floating point ABI.
45 MIPSPKGSFX_ABI - This is used to specify an alternative ABI when the previous
47 building for N32 ABI.
|
| H A D | arch-mips.inc | 5 # *) o32, n32, n64 ABI
13 # ABI flags
14 TUNEVALID[o32] = "MIPS o32 ABI"
18 TUNEVALID[n32] = "MIPS64 n32 ABI"
26 TUNEVALID[n64] = "MIPS64 n64 ABI"
37 # MIPS r6 ABI
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 20 In Linux GPIO lines also have a userspace ABI.
22 The userspace ABI is intended for one-off deployments. Examples are prototypes,
36 Do not under any circumstances abuse the GPIO userspace ABI to cut corners in
41 The userspace ABI is a character device for each GPIO hardware unit (GPIO chip).
43 ``/dev/gpiochipN``. Examples of how to directly use the userspace ABI can be
|
| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_naming_convention.rst | 62 ABI section in API naming convention
83 to be a part of ABI what, in turn, improves both libbpf developer- and
86 ABI versioning
89 To make future ABI extensions possible libbpf ABI is versioned.
96 Every time ABI is being changed, e.g. because a new symbol is added or
97 semantic of existing symbol is changed, ABI version should be bumped.
98 This bump in ABI version is at most once per kernel development cycle.
132 Format of version script and ways to handle ABI changes, including
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | x32-psabi.rst | 8 32-bit processor-specific ABI for Intel 64 (x86-64) architectures. An
9 ABI defines the calling conventions between functions in a processing
15 very old 32-bit ABI for Intel 64-bit platforms. The i386 psABI does not
18 psABI. This ABI is newer and uses 64-bits for data sizes and program
|
| /openbmc/libpldm/ |
| H A D | README.md | 51 Components of the library ABI[^1] (loosely, functions) are separated into three
54 [^1]: ["library API + compiler ABI = library ABI"][libstdc++-library-abi]
87 ### The ABI lifecycle
103 The ABI of the library produced by the build is controlled using the `abi` meson
116 off of deprecated APIs by constraining the library ABI to the stable category.
129 in the library's ABI, any changes to the API risk breaking applications already
169 ### Building a dependent application or library against a testing ABI
176 `libpldm`'s ABI can be controlled from a parent project through meson's
|
| /openbmc/linux/arch/xtensa/ |
| H A D | Kconfig | 300 prompt "Kernel ABI"
303 Select ABI for the kernel code. This ABI is independent of the
311 If unsure, choose the default ABI.
314 bool "Default ABI"
319 cores without it use call0 ABI.
335 prompt "Userspace ABI"
338 Select supported userspace ABI.
343 bool "Default ABI only"
345 Assume default userspace ABI. For XEA2 cores it is windowed ABI.
350 bool "Call0 ABI only"
[all …]
|
| /openbmc/openbmc/poky/meta/conf/machine/include/powerpc/ |
| H A D | arch-powerpc64.inc | 5 TUNEVALID[m64] = "Power ELF64 standard ABI"
10 # musl only supports elfv2 ABI for ppc64
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | vdso | 13 your platform's ABI. Call them from a sensible context. (For example,
29 ABI of those symbols is considered stable. It may vary across architectures,
33 As of this writing, this ABI documentation as been confirmed for x86_64.
|
| /openbmc/linux/Documentation/ABI/removed/ |
| H A D | raw1394 | 11 Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
15 libraw1394 (works with firewire-cdev too, transparent to library ABI
|
| H A D | video1394 | 12 Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
16 libdc1394 (works with firewire-cdev too, transparent to library ABI
|
| /openbmc/linux/Documentation/virt/kvm/devices/ |
| H A D | arm-vgic-its.rst | 60 The layout of the tables in guest memory defines an ABI. The entries
71 encodes the ABI revision.
108 - GITS_IIDR. The Revision field encodes the table layout ABI revision.
111 the ABI. GITS_IIDR must be restored before calling
144 ITS Table ABI REV0:
147 Revision 0 of the ABI only supports the features of a virtual GICv3, and does
211 - The ABI version is unchanged and remains the one set when the ITS
|