Home
last modified time | relevance | path

Searched refs:architectures (Results 226 – 250 of 425) sorted by relevance

12345678910>>...17

/openbmc/linux/tools/perf/arch/mips/entry/syscalls/
H A Dsyscall_n64.tbl340 # 329 through 423 are reserved to sync up with other architectures
/openbmc/linux/Documentation/driver-api/
H A Deisa.rst24 among all the architectures that the EISA code runs on. It
/openbmc/linux/Documentation/arch/x86/
H A Dkernel-stacks.rst14 Like all other architectures, x86_64 has a kernel stack for every
/openbmc/linux/arch/mips/kernel/syscalls/
H A Dsyscall_n64.tbl340 # 329 through 423 are reserved to sync up with other architectures
/openbmc/linux/arch/ia64/kernel/syscalls/
H A Dsyscall.tbl346 # 334 through 423 are reserved to sync up with other architectures
/openbmc/linux/arch/loongarch/
H A DKconfig215 # are shared between architectures, and specifically expecting the symbols.
622 for architectures which are either NUMA (Non-Uniform Memory Access)
/openbmc/openbmc/poky/meta/recipes-kernel/perf/
H A Dperf.bb39 # libunwind is not yet ported for some architectures
132 # the architectures that need this file can be found in
/openbmc/linux/mm/
H A DKconfig540 # Only be set on architectures that have completely implemented memory hotplug
860 For selection by architectures with reasonable THP sizes.
1085 suitable for 64-bit architectures with CONFIG_FLATMEM or
1144 # Some architectures require a special hugepage directory format that is
/openbmc/linux/Documentation/admin-guide/mm/
H A Dmemory-hotplug.rst35 Linux only supports memory hot(un)plug on selected 64 bit architectures, such as
114 On some architectures, the firmware may not be able to notify the operating
617 - Huge pages are unmovable when an architectures does not support huge
H A Dpagemap.rst227 always 12 at most architectures). Since Linux 3.11 their meaning changes
/openbmc/linux/Documentation/dev-tools/
H A Dgcov.rst43 on all architectures.
/openbmc/openbmc-tools/ipkdbg/
H A DREADME.md126 `ipkdbg` supports multiple distros and architectures by defining a directory
/openbmc/linux/Documentation/mm/
H A Dmemory-model.rst39 maps the entire physical memory. For most architectures, the holes
/openbmc/linux/Documentation/arch/arm/
H A Darm.rst104 as such Acorn RiscPCs and other architectures using these processors can
/openbmc/linux/drivers/base/
H A DKconfig222 Enable support for architectures common topology code: e.g., parsing
/openbmc/linux/Documentation/fb/
H A Dmatroxfb.rst94 architectures there are some glitches for 24bpp videomodes. 8, 16 and 32bpp
316 - 24bpp does not support correctly XF-FBDev on big-endian architectures.
/openbmc/linux/tools/objtool/Documentation/
H A Dobjtool.txt120 For some architectures, frame pointers are enabled by
121 CONFIG_FRAME_POINTER. For some other architectures they may be
/openbmc/linux/Documentation/core-api/
H A Dcachetlb.rst357 architectures). For incoherent architectures, it should flush
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dbuilding.rst681 architectures: "all", "tune" or "package", and "machine". Any given
682 recipe usually selects one of these package architectures (types) for
691 This class is useful for "all" architectures because it configures
692 many variables so packages can be used across multiple architectures.
/openbmc/linux/Documentation/kbuild/
H A Dmakefiles.rst1296 The actual goals are not standardized across architectures.
1453 that may be shared between individual architectures.
1465 for architectures to run post-link passes on. Must also handle
1502 avoid exporting specific headers (e.g. kvm.h) on architectures that do
1553 to define the minimum set of ASM headers that all architectures must have.
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst437 On architectures where unaligned accesses cause traps, and where this
1133 space randomization that is used in the system, for architectures
1138 default for architectures that do not support this feature anyways,
1355 This feature is only applicable for architectures which support
1560 On architectures where unaligned accesses cause traps, and where this
/openbmc/linux/Documentation/filesystems/
H A Dromfs.rst189 - Does it work on other architectures than intel and motorola?
/openbmc/u-boot/doc/
H A DREADME.fdt-control215 architectures.
/openbmc/linux/Documentation/input/
H A Dinput.rst89 event codes are the same on all architectures and are hardware
/openbmc/linux/tools/perf/Documentation/
H A Djitdump-specification.txt21 … is self-describing in terms of endianness and is portable across multiple processor architectures.

12345678910>>...17