Searched refs:architectures (Results 1 – 25 of 200) sorted by relevance
12345678
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | vdso | 1 On some architectures, when the kernel loads any userspace program it
23 ABI of those symbols is considered stable. It may vary across architectures,
27 The maintainers of the other vDSO-using architectures should confirm
|
| /Linux-v5.4/Documentation/arm/ |
| D | setup.rst | 7 for most ARM Linux architectures.
61 based machines. May be used differently by different architectures.
65 different architectures.
69 architectures.
102 then a value of 50 Mhz is the default on 21285 architectures.
|
| /Linux-v5.4/Documentation/ |
| D | unaligned-memory-access.txt | 13 Linux runs on a wide variety of architectures which have varying behaviour
46 In reality, only a few architectures require natural alignment on all sizes
47 of memory access. However, we must consider ALL supported architectures;
59 - Some architectures are able to perform unaligned memory accesses
61 - Some architectures raise processor exceptions when unaligned accesses
64 - Some architectures raise processor exceptions when unaligned accesses
67 - Some architectures are not capable of unaligned memory access, but will
246 On architectures that require aligned loads, networking requires that the IP
249 architectures this constant has the value 2 because the normal ethernet
258 unnecessary on architectures that can do unaligned accesses, the code can be
|
| D | atomic_t.txt | 152 are time critical and can, (typically) on LL/SC architectures, be more
201 These helper barriers exist because architectures have varying implicit
202 ordering on their SMP atomic primitives. For example our TSO architectures
|
| /Linux-v5.4/Documentation/bpf/ |
| D | bpf_design_QA.rst | 34 with two most used architectures x64 and arm64 (and takes into
35 consideration important quirks of other architectures) and
37 convention of the linux kernel on those architectures.
135 impossible to make generic and efficient across CPU architectures.
150 A: Because architectures like sparc have register windows and in general
151 there are enough subtle differences between architectures, so naive
172 CPU architectures and 32-bit HW accelerators. Can true 32-bit registers
179 programs for 32-bit architectures.
186 (a mov32 variant). This means that for architectures without zext hardware
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | v4l2-clocks.rst | 14 this purpose. However, it is not (yet) available on all architectures. Besides,
31 architectures this API will be removed.
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cputopology.rst | 6 to /proc/cpuinfo output of some architectures. They reside in
113 To be consistent on all architectures, include/linux/topology.h
124 For architectures that don't support books (CONFIG_SCHED_BOOK) there are no
126 For architectures that don't support drawers (CONFIG_SCHED_DRAWER) there are
|
| D | highuid.rst | 15 What's left to be done for 32-bit UIDs on all Linux architectures:
23 architectures, this should not be a problem.
|
| /Linux-v5.4/kernel/configs/ |
| D | nopm.config | 11 # ARM/ARM64 architectures that select PM unconditionally
|
| /Linux-v5.4/include/asm-generic/ |
| D | Kbuild | 3 # asm headers that all architectures except um should have
|
| /Linux-v5.4/Documentation/vm/ |
| D | numa.rst | 51 architectures. As with physical cells, software nodes may contain 0 or more
57 For some architectures, such as x86, Linux will "hide" any node representing a
60 these architectures, one cannot assume that all CPUs that Linux associates with
63 In addition, for some architectures, again x86 is an example, Linux supports
119 On architectures that do not hide memoryless nodes, Linux will include only
147 architectures transparently, kernel subsystems can use the numa_mem_id()
|
| /Linux-v5.4/Documentation/features/ |
| D | arch-support.txt | 4 support matrix, for all upstream Linux architectures.
|
| /Linux-v5.4/lib/vdso/ |
| D | Kconfig | 20 in 32 bit only architectures.
|
| /Linux-v5.4/sound/mips/ |
| D | Kconfig | 9 Support for sound devices of MIPS architectures.
|
| /Linux-v5.4/sound/parisc/ |
| D | Kconfig | 9 Support for GSC sound devices on PA-RISC architectures.
|
| /Linux-v5.4/arch/ |
| D | Kconfig | 137 Some architectures are unable to perform unaligned accesses
170 on architectures that don't have such instructions.
289 All new 32-bit architectures should have 64-bit off_t type on
291 is the requirement for modern ABIs. Some existing architectures
293 architectures explicitly.
388 architectures.
802 This should be selected by all architectures that need to support
804 architectures, and 64-bit architectures as part of compat syscall
811 This is relevant on all 32-bit architectures, and 64-bit architectures
830 This may rule out many 32-bit architectures.
[all …]
|
| /Linux-v5.4/Documentation/ioctl/ |
| D | ioctl-decoding.rst | 7 Most architectures use this generic format, but check
|
| /Linux-v5.4/sound/sh/ |
| D | Kconfig | 9 Support for sound devices specific to SUPERH architectures.
|
| /Linux-v5.4/arch/c6x/ |
| D | Kconfig | 63 On some architectures there is currently no way for the boot loader
64 to pass arguments to the kernel. For these architectures, you should
|
| /Linux-v5.4/sound/arm/ |
| D | Kconfig | 9 Support for sound devices specific to ARM architectures.
|
| /Linux-v5.4/Documentation/arm/omap/ |
| D | omap_pm.rst | 23 - allow drivers which are shared with other architectures (e.g.,
28 architectures.
77 omap_pm_set_max_dev_wakeup_lat(), etc. Other architectures which do
|
| /Linux-v5.4/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 12 architectures that typically run big-endian operating systems
|
| /Linux-v5.4/arch/x86/um/ |
| D | Kconfig | 43 However, this it experimental on 32-bit architectures, so if unsure say
|
| /Linux-v5.4/sound/sparc/ |
| D | Kconfig | 9 Support for sound devices specific to Sun SPARC architectures.
|
| /Linux-v5.4/arch/arm/mach-aspeed/ |
| D | Kconfig | 3 bool "Aspeed BMC architectures"
|
12345678
