Searched full:architectures (Results 1 – 25 of 1697) sorted by relevance
12345678910>>...68
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/arch/arm/include/asm/ |
| D | dma.h | 68 * Some architectures may need to do allocate an interrupt
74 * Some architectures may need to do free an interrupt
80 * On some architectures, this may have other side effects like
87 * On some architectures, this may have other side effects like
99 * especially since some DMA architectures don't update the
107 * especially since some DMA architectures don't update the
117 * especially since some DMA architectures don't update the
125 * especially since some DMA architectures don't update the
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| D | api.rst | 106 Architectures:
107 which instruction set architectures provide this ioctl.
125 :Architectures: all
142 :Architectures: all
198 :Architectures: x86
240 :Architectures: all
259 :Architectures: all
273 :Architectures: all
285 :Architectures: all
332 :Architectures: all
[all …]
|
| /kernel/linux/linux-6.6/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
326 :Architectures: all
364 :Architectures: all
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/arch/ |
| D | Kconfig | 143 Some architectures require 64 bit accesses to be 64 bit
146 architectures which can do 64 bit accesses, as well as 64 bit
147 architectures without unaligned access.
159 Some architectures are unable to perform unaligned accesses
192 on architectures that don't have such instructions.
303 # Select if the architectures provides the arch_dma_clear_uncached symbol
350 All new 32-bit architectures should have 64-bit off_t type on
352 is the requirement for modern ABIs. Some existing architectures
354 architectures explicitly.
356 # Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustat
[all …]
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | types.h | 43 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
45 * aligned_64 values have the same alignment on 32-bit and 64-bit architectures.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/include/uapi/asm-generic/ |
| 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.
|
| /kernel/linux/linux-5.10/arch/ |
| D | Kconfig | 149 Some architectures require 64 bit accesses to be 64 bit
152 architectures which can do 64 bit accesses, as well as 64 bit
153 architectures without unaligned access.
165 Some architectures are unable to perform unaligned accesses
198 on architectures that don't have such instructions.
287 # 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.
420 architectures.
[all …]
|
| /kernel/linux/linux-6.6/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
|
12345678910>>...68