Searched full:architectures (Results 1 – 25 of 858) sorted by relevance
12345678910>>...35
| /Linux-v6.1/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 20 debugging are unsound for livepatching. Livepatching depends on architectures
28 Architectures must implement one of the reliable stacktrace functions.
29 Architectures using CONFIG_ARCH_STACKWALK must implement
30 'arch_stack_walk_reliable', and other architectures must implement
56 architectures may need to verify that code has been compiled in a manner
59 functions use specific prologue and epilogue sequences. Architectures
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
[all …]
|
| /Linux-v6.1/arch/arm/include/asm/ |
| D | dma.h | 65 * Some architectures may need to do allocate an interrupt
71 * Some architectures may need to do free an interrupt
77 * On some architectures, this may have other side effects like
84 * On some architectures, this may have other side effects like
96 * especially since some DMA architectures don't update the
104 * especially since some DMA architectures don't update the
114 * especially since some DMA architectures don't update the
122 * especially since some DMA architectures don't update the
|
| /Linux-v6.1/Documentation/virt/kvm/ |
| D | api.rst | 106 Architectures:
107 which instruction set architectures provide this ioctl.
125 :Architectures: all
142 :Architectures: all
192 :Architectures: x86
234 :Architectures: all
253 :Architectures: all
279 :Architectures: all
291 :Architectures: all
338 :Architectures: all
[all …]
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/arch/ |
| D | Kconfig | 122 Some architectures require 64 bit accesses to be 64 bit
125 architectures which can do 64 bit accesses, as well as 64 bit
126 architectures without unaligned access.
138 Some architectures are unable to perform unaligned accesses
171 on architectures that don't have such instructions.
282 # Select if the architectures provides the arch_dma_clear_uncached symbol
326 All new 32-bit architectures should have 64-bit off_t type on
328 is the requirement for modern ABIs. Some existing architectures
330 architectures explicitly.
332 # Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustat
[all …]
|
| /Linux-v6.1/include/asm-generic/ |
| D | access_ok.h | 7 * These definitions work on most architectures, but overrides can
12 * architectures with compat tasks have a variable TASK_SIZE and should
24 * On architectures with separate user address space (m68k, s390, parisc,
|
| /Linux-v6.1/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-v6.1/include/uapi/asm-generic/ |
| D | sembuf.h | 9 * The semid64_ds structure for most architectures (though it came from x86_32
17 * 64 bit architectures use a 64-bit long time field here, while
18 * 32 bit architectures have a pair of unsigned long values.
|
| D | posix_types.h | 11 * architectures, so that you can override them.
63 * Most 32 bit architectures use "unsigned int" size_t,
64 * and all 64 bit architectures use "unsigned long" size_t.
|
| D | stat.h | 7 * eternity. Hopefully, this version gets used by new architectures
14 * By convention, 64 bit architectures use the stat interface, while
15 * 32 bit architectures use the stat64 interface. Note that we don't
|
| /Linux-v6.1/Documentation/mm/ |
| 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-v6.1/arch/um/include/shared/ |
| D | ptrace_user.h | 24 /* On architectures, that started to support PTRACE_O_TRACESYSGOOD
28 * PTRACE_OLDSETOPTION. On these architectures, UML always must use
35 * On architectures, that start to support PTRACE_O_TRACESYSGOOD on
|
| /Linux-v6.1/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-v6.1/include/uapi/linux/ |
| D | types.h | 46 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
48 * aligned_64 values have the same alignment on 32-bit and 64-bit architectures.
|
| /Linux-v6.1/arch/riscv/include/asm/ |
| D | bitops.h | 69 * This operation may be reordered on other architectures than x86.
81 * This operation can be reordered on other architectures other than x86.
107 * on non x86 architectures, so if you are writing portable code,
124 * on non x86 architectures, so if you are writing portable code,
137 * change_bit() may be reordered on other architectures than x86.
|
| /Linux-v6.1/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-v6.1/drivers/hv/ |
| D | hv_common.c | 29 * specific globals so they are shared across all architectures and are
56 * common across all architectures. Called from architecture
118 * individual CPUs that is common across all architectures.
241 * architectures where it is used, Hyper-V enlightenment code in
253 * may be overridden by architecture specific versions. Architectures
|
| /Linux-v6.1/lib/vdso/ |
| D | Kconfig | 20 in 32 bit only architectures.
30 Selected by architectures which support time namespaces in the
|
| /Linux-v6.1/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-v6.1/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
|
| /Linux-v6.1/include/linux/byteorder/ |
| D | generic.h | 11 * some architectures. Use get_unaligned for unaligned data.
38 * see how some architectures already do (i386, alpha, ppc, etc)
43 * architectures (and F21 Linux addict around?).
69 * 64-bit stuff only defined for proper architectures
|
| /Linux-v6.1/include/linux/ |
| D | highuid.h | 20 * uid16_t and gid16_t are used on all architectures. (when dealing
74 * Everything below this line is needed on all architectures, to deal with
89 * Since these macros are used in architectures that only need limited
|
| /Linux-v6.1/arch/microblaze/ |
| D | Kconfig | 53 microblaze architectures can be configured for either little or
104 On some architectures there is currently no way for the boot loader
105 to pass arguments to the kernel. For these architectures, you should
|
12345678910>>...35
