Searched full:architectures (Results 1 – 25 of 211) sorted by relevance
123456789
| /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 …]
|
| /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.
|
| /Documentation/ABI/stable/ |
| D | vdso | 7 On some architectures, when the kernel loads any userspace program it
31 ABI of those symbols is considered stable. It may vary across architectures,
36 The maintainers of the other vDSO-using architectures should confirm
|
| /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 …]
|
| /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
|
| D | floating-point.rst | 27 Several architectures implement the generic kernel floating-point API from
28 ``linux/fpu.h``, as described below. Some other architectures implement their
41 Architectures are expected to define one or both of these variables in their
|
| /Documentation/virt/kvm/ |
| D | api.rst | 106 Architectures:
107 which instruction set architectures provide this ioctl.
125 :Architectures: all
142 :Architectures: all
211 :Architectures: x86
253 :Architectures: all
272 :Architectures: all
298 :Architectures: all
345 :Architectures: all
383 :Architectures: all
[all …]
|
| /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()
|
| /Documentation/arch/powerpc/ |
| D | elf_hwcaps.rst | 148 supporting later architectures DO NOT set this feature.
161 supporting later architectures also set this feature.
183 supporting later architectures also set this feature.
210 supporting later architectures also set this feature.
229 supporting later architectures also set this feature.
|
| /Documentation/devicetree/bindings/tpm/ |
| D | microsoft,ftpm.yaml | 14 Commodity CPU architectures, such as ARM and Intel CPUs, have started to
16 trusted hardware. Unfortunately, these CPU architectures raise serious
|
| /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
|
| /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
|
| /Documentation/features/ |
| D | arch-support.txt | 4 support matrix, for all upstream Linux architectures.
|
| /Documentation/arch/ |
| D | index.rst | 3 CPU Architectures
|
| /Documentation/gpu/amdgpu/ |
| D | index.rst | 6 Next (GCN), Radeon DNA (RDNA), and Compute DNA (CDNA) architectures.
|
| /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
|
| D | efi-stub.rst | 14 between architectures is in drivers/firmware/efi/libstub.
86 For the ARM and arm64 architectures, a device tree must be provided to
|
| /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
|
| /Documentation/devicetree/bindings/serial/ |
| D | litex,liteuart.yaml | 16 multiple CPU architectures, currently including e.g. OpenRISC and RISC-V.
|
| /Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 12 architectures that typically run big-endian operating systems
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 25 Does KUnit support running on architectures other than UML?
34 (``tools/testing/kunit/kunit.py``) that might not support some architectures
37 In short, yes, you can run KUnit on other architectures, but it might require
|
| /Documentation/arch/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
|
| /Documentation/core-api/irq/ |
| D | concepts.rst | 21 Architectures can assign additional meaning to the IRQ numbers, and
|
| /Documentation/admin-guide/mm/ |
| D | concepts.rst | 23 address ranges. Besides, different CPU architectures, and even
42 size of each page is architecture specific. Some architectures allow
75 Many modern CPU architectures allow mapping of the memory pages
112 architectures define all zones, and requirements for DMA are different
|
123456789