Home
last modified time | relevance | path

Searched refs:architectures (Results 1 – 25 of 174) sorted by relevance

1234567

/linux/Documentation/arch/arm/
H A Dsetup.rst7 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/virt/kvm/
H A DKconfig23 # Only strongly ordered architectures can select this, as it doesn't
31 # Weakly ordered architectures can only select this, advertising
37 # Allow enabling both the dirty bitmap and dirty ring. Only architectures
/linux/Documentation/ABI/stable/
H A Dvdso7 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
/linux/Documentation/livepatch/
H A Dreliable-stacktrace.rst20 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/tools/testing/selftests/nolibc/
H A Drun-tests.sh45 Run nolibc testsuite for multiple architectures with crosstools
48 $0 [options] <architectures>
50 Known architectures:
/linux/Documentation/core-api/
H A Dunaligned-memory-access.rst13 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/Documentation/
H A Datomic_t.txt152 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/fs/resctrl/
H A DKconfig7 Some architectures provide hardware facilities to group tasks and
21 On architectures where this can be disabled independently, it is
/linux/Documentation/arch/powerpc/
H A Delf_hwcaps.rst148 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.
/linux/tools/include/nolibc/
H A DMakefile20 architectures := \ macro
37 arch_files := arch.h $(addsuffix .h, $(addprefix arch-, $(architectures)))
/linux/Documentation/bpf/
H A Dbpf_design_QA.rst34 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
/linux/kernel/configs/
H A Dnopm.config13 # ARM/ARM64 architectures that select PM unconditionally
/linux/arch/
H A DKconfig21 # Selected by architectures that need custom DMA operations for e.g. legacy
214 Some architectures require 64 bit accesses to be 64 bit
217 architectures which can do 64 bit accesses, as well as 64 bit
218 architectures without unaligned access.
230 Some architectures are unable to perform unaligned accesses
260 on architectures that don't have such instructions.
371 # Select if the architectures provides the arch_dma_clear_uncached symbol
413 All new 32-bit architectures should have 64-bit off_t type on
415 is the requirement for modern ABIs. Some existing architectures
417 architectures explicitly.
[all …]
/linux/Documentation/features/
H A Darch-support.txt4 support matrix, for all upstream Linux architectures.
/linux/sound/parisc/
H A DKconfig9 Support for GSC sound devices on PA-RISC architectures.
/linux/Documentation/userspace-api/ioctl/
H A Dioctl-decoding.rst7 Most architectures use this generic format, but check
/linux/sound/mips/
H A DKconfig9 Support for sound devices of MIPS architectures.
/linux/Documentation/admin-guide/
H A Dcputopology.rst6 to /proc/cpuinfo output of some architectures. They reside in
36 To be consistent on all architectures, include/linux/topology.h
/linux/Documentation/arch/arm/omap/
H A Domap_pm.rst23 - 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
/linux/arch/microblaze/
H A DKconfig55 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/sound/sh/
H A DKconfig9 Support for sound devices specific to SUPERH architectures.
/linux/sound/arm/
H A DKconfig9 Support for sound devices specific to ARM architectures.
/linux/drivers/firmware/smccc/
H A DKconfig6 Call (HVC) instructions on Armv7 and above architectures.
/linux/Documentation/devicetree/bindings/regmap/
H A Dregmap.txt12 architectures that typically run big-endian operating systems
/linux/sound/sparc/
H A DKconfig9 Support for sound devices specific to Sun SPARC architectures.

1234567