Searched refs:architectures (Results 1 – 25 of 238) sorted by relevance
12345678910
| /linux-5.19.10/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-5.19.10/lib/vdso/ |
| D | Kconfig | 20 in 32 bit only architectures.
30 Selected by architectures which support time namespaces in the
|
| /linux-5.19.10/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-5.19.10/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-5.19.10/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-5.19.10/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-5.19.10/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-5.19.10/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-5.19.10/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()
|
| D | vmemmap_dedup.rst | 15 architectures. See Documentation/admin-guide/mm/hugetlbpage.rst for more
29 Different architectures support different HugeTLB pages. For example, the
31 architectures. Because arm64 supports 4k, 16k, and 64k base pages and
163 Apart from the HugeTLB page of the pmd/pud level mapping, some architectures
|
| /linux-5.19.10/kernel/configs/ |
| D | nopm.config | 11 # ARM/ARM64 architectures that select PM unconditionally
|
| /linux-5.19.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 25 Does KUnit support running on architectures other than UML?
34 (``tools/testing/kunit/kunit.py``) that does not support other architectures.
36 In short, yes, you can run KUnit on other architectures, but it might require
99 non-UML architectures" in Documentation/dev-tools/kunit/usage.rst.
|
| /linux-5.19.10/Documentation/features/ |
| D | arch-support.txt | 4 support matrix, for all upstream Linux architectures.
|
| /linux-5.19.10/sound/parisc/ |
| D | Kconfig | 9 Support for GSC sound devices on PA-RISC architectures.
|
| /linux-5.19.10/Documentation/devicetree/bindings/serial/ |
| D | litex,liteuart.yaml | 16 multiple CPU architectures, currently including e.g. OpenRISC and RISC-V.
|
| /linux-5.19.10/sound/mips/ |
| D | Kconfig | 9 Support for sound devices of MIPS architectures.
|
| /linux-5.19.10/Documentation/userspace-api/ioctl/ |
| D | ioctl-decoding.rst | 7 Most architectures use this generic format, but check
|
| /linux-5.19.10/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.
|
| D | cputopology.rst | 6 to /proc/cpuinfo output of some architectures. They reside in
36 To be consistent on all architectures, include/linux/topology.h
|
| /linux-5.19.10/arch/ |
| D | Kconfig | 123 Some architectures require 64 bit accesses to be 64 bit
126 architectures which can do 64 bit accesses, as well as 64 bit
127 architectures without unaligned access.
139 Some architectures are unable to perform unaligned accesses
172 on architectures that don't have such instructions.
283 # Select if the architectures provides the arch_dma_clear_uncached symbol
327 All new 32-bit architectures should have 64-bit off_t type on
329 is the requirement for modern ABIs. Some existing architectures
331 architectures explicitly.
333 # Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustat
[all …]
|
| /linux-5.19.10/arch/microblaze/ |
| D | Kconfig | 55 microblaze architectures can be configured for either little or
106 On some architectures there is currently no way for the boot loader
107 to pass arguments to the kernel. For these architectures, you should
|
| /linux-5.19.10/sound/sh/ |
| D | Kconfig | 9 Support for sound devices specific to SUPERH architectures.
|
| /linux-5.19.10/sound/arm/ |
| D | Kconfig | 9 Support for sound devices specific to ARM architectures.
|
| /linux-5.19.10/drivers/firmware/smccc/ |
| D | Kconfig | 6 Call (HVC) instructions on Armv7 and above architectures.
|
| /linux-5.19.10/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
|
12345678910