Searched full:architectures (Results 1 – 25 of 787) sorted by relevance
12345678910>>...32
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | api.rst | 106 Architectures:
107 which instruction set architectures provide this ioctl.
125 :Architectures: all
142 :Architectures: all
195 :Architectures: x86
237 :Architectures: all
256 :Architectures: all
270 :Architectures: all
282 :Architectures: all
329 :Architectures: all
[all …]
|
| /Linux-v5.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-v5.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-v5.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-v5.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()
|
| /Linux-v5.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
|
| /Linux-v5.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.
|
| /Linux-v5.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.
|
| 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
|
| D | termios.h | 5 * Most architectures have straight copies of the x86 code, with
9 * New architectures should not provide their own version.
|
| D | msgbuf.h | 18 * 64 bit architectures use a 64-bit long time field here, while
19 * 32 bit architectures have a pair of unsigned long values.
|
| D | sembuf.h | 17 * 64 bit architectures use a 64-bit long time field here, while
18 * 32 bit architectures have a pair of unsigned long values.
|
| /Linux-v5.10/arch/ |
| D | Kconfig | 149 Some architectures are unable to perform unaligned accesses
182 on architectures that don't have such instructions.
271 # Select if the architectures provides the arch_dma_clear_uncached symbol
308 All new 32-bit architectures should have 64-bit off_t type on
310 is the requirement for modern ABIs. Some existing architectures
312 architectures explicitly.
401 architectures.
429 Temporary select until all architectures can be converted to have
430 irqs disabled over activate_mm. Architectures that do IPI based TLB
881 This is relevant on all 32-bit architectures, and 64-bit architectures
[all …]
|
| /Linux-v5.10/arch/riscv/include/asm/ |
| D | bitops.h | 70 * This operation may be reordered on other architectures than x86.
82 * This operation can be reordered on other architectures other than x86.
108 * on non x86 architectures, so if you are writing portable code,
125 * on non x86 architectures, so if you are writing portable code,
138 * change_bit() may be reordered on other architectures than x86.
|
| /Linux-v5.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-v5.10/lib/vdso/ |
| D | Kconfig | 20 in 32 bit only architectures.
30 Selected by architectures which support time namespaces in the
|
| /Linux-v5.10/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
|
| /Linux-v5.10/include/asm-generic/ |
| D | hyperv-tlfs.h | 20 * size may not be 4096 on all architectures.
31 * and B definitions are common across architectures and are listed here.
32 * However, not all flags are relevant on all architectures.
34 * Groups C and D vary across architectures and are listed in the
36 * on multiple architectures, but the bit positions are different so they
41 * group of 32 bits, but they vary across architectures and are listed in
|
| /Linux-v5.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 25 Does KUnit support running on architectures other than UML?
35 other architectures.
37 In short, this means that, yes, you can run KUnit on other architectures, but
100 non-UML architectures" in :doc:`usage`.
|
| /Linux-v5.10/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-v5.10/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-v5.10/usr/ |
| D | initramfs_data.S | 17 The above example is for i386 - the parameters vary from architectures.
22 in the ELF header, as required by certain architectures.
|
| /Linux-v5.10/include/scsi/ |
| D | srp.h | 107 * having the 20-byte structure padded to 24 bytes on 64-bit architectures.
172 * bytes on 64-bit architectures.
262 * 64-bit architectures.
297 * on 64-bit architectures.
|
| /Linux-v5.10/Documentation/driver-api/media/ |
| D | v4l2-clocks.rst | 14 this purpose. However, it is not (yet) available on all architectures. Besides,
31 architectures this API will be removed.
|
12345678910>>...32
