Searched refs:architectures (Results 1 – 25 of 252) sorted by relevance
1234567891011
| /linux-6.6.21/virt/kvm/ |
| D | Kconfig | 22 # Only strongly ordered architectures can select this, as it doesn't
30 # Weakly ordered architectures can only select this, advertising
36 # Allow enabling both the dirty bitmap and dirty ring. Only architectures
|
| /linux-6.6.21/Documentation/arch/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-6.6.21/Documentation/ABI/stable/ |
| D | vdso | 7 On some architectures, when the kernel loads any userspace program it
29 ABI of those symbols is considered stable. It may vary across architectures,
34 The maintainers of the other vDSO-using architectures should confirm
|
| /linux-6.6.21/lib/vdso/ |
| D | Kconfig | 20 in 32 bit only architectures.
30 Selected by architectures which support time namespaces in the
|
| /linux-6.6.21/Documentation/rust/ |
| D | arch-support.rst | 7 which limits the supported architectures that can be targeted. In addition,
12 Below is a general summary of architectures that currently work. Level of
|
| /linux-6.6.21/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 20 debugging are unsound for livepatching. Livepatching depends on architectures
30 'arch_stack_walk_reliable', and other architectures must implement
56 architectures may need to verify that code has been compiled in a manner
71 The unwinding process varies across architectures, their respective procedure
73 details that architectures should consider.
89 architectures verify that a stacktrace ends at an expected location, e.g.
116 trace, it is strongly recommended that architectures positively identify code
140 For some architectures this may change at runtime as a result of dynamic
219 It is recommended that architectures unwind cases where return_to_handler has
220 not yet been returned to, but architectures are not required to unwind from the
[all …]
|
| /linux-6.6.21/Documentation/driver-api/ |
| D | device-io.rst | 31 memory, but as accesses to a device. Some architectures define devices
44 space to the kernel. Most architectures allocate new address space each
153 ``void __iomem *reg``. On most architectures it is a regular pointer that
160 While on most architectures, ioremap() creates a page table entry for an
162 architectures require special instructions for MMIO, and the ``__iomem`` pointer
182 On architectures that require an expensive barrier for serializing against
197 for mapping PCI I/O space with pci_iomap() or ioport_map(). On architectures
200 other architectures, these are simply aliases.
211 Note: On some architectures, the normal readl()/writel() functions
223 on 32-bit architectures but allow two consecutive 32-bit accesses instead.
[all …]
|
| /linux-6.6.21/Documentation/core-api/ |
| D | unaligned-memory-access.rst | 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
|
| /linux-6.6.21/Documentation/ |
| 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
326 indefinitely. However, this is not evident on LL/SC architectures, because
357 to fail on some architectures, let alone whatever the compiler makes of the C
361 Even native CAS architectures can fail to provide forward progress for their
365 to a failed CAS in order to ensure some progress. Affected architectures are
|
| /linux-6.6.21/Documentation/powerpc/ |
| D | elf_hwcaps.rst | 147 supporting later architectures DO NOT set this feature.
160 supporting later architectures also set this feature.
182 supporting later architectures also set this feature.
209 supporting later architectures also set this feature.
228 supporting later architectures also set this feature.
|
| /linux-6.6.21/drivers/gpu/drm/amd/display/ |
| D | Kconfig | 18 architectures built with Clang (all released versions), whereby the stack
20 panic on most architectures. We'll revert this when the following bug report
|
| /linux-6.6.21/Documentation/mm/ |
| D | numa.rst | 49 architectures. As with physical cells, software nodes may contain 0 or more
55 For some architectures, such as x86, Linux will "hide" any node representing a
58 these architectures, one cannot assume that all CPUs that Linux associates with
61 In addition, for some architectures, again x86 is an example, Linux supports
117 On architectures that do not hide memoryless nodes, Linux will include only
145 architectures transparently, kernel subsystems can use the numa_mem_id()
|
| /linux-6.6.21/kernel/configs/ |
| D | nopm.config | 13 # ARM/ARM64 architectures that select PM unconditionally
|
| /linux-6.6.21/Documentation/gpu/amdgpu/ |
| D | index.rst | 6 Next (GCN), Radeon DNA (RDNA), and Compute DNA (CDNA) architectures.
|
| /linux-6.6.21/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.
145 A: Because architectures like sparc have register windows and in general
146 there are enough subtle differences between architectures, so naive
167 CPU architectures and 32-bit HW accelerators. Can true 32-bit registers
174 programs for 32-bit architectures.
181 (a mov32 variant). This means that for architectures without zext hardware
|
| /linux-6.6.21/Documentation/features/ |
| D | arch-support.txt | 4 support matrix, for all upstream Linux architectures.
|
| /linux-6.6.21/sound/parisc/ |
| D | Kconfig | 9 Support for GSC sound devices on PA-RISC architectures.
|
| /linux-6.6.21/sound/mips/ |
| D | Kconfig | 9 Support for sound devices of MIPS architectures.
|
| /linux-6.6.21/Documentation/devicetree/bindings/serial/ |
| D | litex,liteuart.yaml | 16 multiple CPU architectures, currently including e.g. OpenRISC and RISC-V.
|
| /linux-6.6.21/Documentation/userspace-api/ioctl/ |
| D | ioctl-decoding.rst | 7 Most architectures use this generic format, but check
|
| /linux-6.6.21/Documentation/admin-guide/ |
| 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-6.6.21/arch/microblaze/ |
| D | Kconfig | 54 microblaze architectures can be configured for either little or
105 On some architectures there is currently no way for the boot loader
106 to pass arguments to the kernel. For these architectures, you should
|
| /linux-6.6.21/sound/sh/ |
| D | Kconfig | 9 Support for sound devices specific to SUPERH architectures.
|
| /linux-6.6.21/sound/arm/ |
| D | Kconfig | 9 Support for sound devices specific to ARM architectures.
|
| /linux-6.6.21/drivers/firmware/smccc/ |
| D | Kconfig | 6 Call (HVC) instructions on Armv7 and above architectures.
|
1234567891011