Searched full:architecture (Results 1 – 25 of 1898) sorted by relevance
12345678910>>...76
| /Linux-v6.1/arch/x86/crypto/ |
| D | Kconfig | 13 Architecture: x86_64 using:
29 Architecture: x86 (32-bit and 64-bit) using:
42 Architecture: x86_64
53 Architecture: x86_64
65 Architecture: x86_64 using:
76 Architecture: x86_64 using:
92 Architecture: x86_64 using:
110 Architecture: x86_64 using:
125 Architecture: x86_64
140 Architecture: x86_64 using:
[all …]
|
| /Linux-v6.1/arch/arm64/crypto/ |
| D | Kconfig | 15 Architecture: arm64 using:
25 Architecture: arm64 using:
36 Architecture: arm64 using:
47 Architecture: arm64 using:
56 Architecture: arm64
66 Architecture: arm64 using:
75 Architecture: arm64
85 Architecture: arm64 using:
96 Architecture: arm64 using:
107 Architecture: arm64 using:
[all …]
|
| /Linux-v6.1/arch/arm/crypto/ |
| D | Kconfig | 13 Architecture: arm with
25 Architecture: arm using
42 Architecture: arm using:
52 Architecture: arm optionally using
61 Architecture: arm
75 Architecture: arm using
91 Architecture: arm
102 Architecture: arm using
113 Architecture: arm using ARMv8 Crypto Extensions
123 Architecture: arm using
[all …]
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | isa-versions.rst | 10 CPU Architecture version
24 Power5 - PowerPC User Instruction Set Architecture Book I v2.02
25 - PowerPC Virtual Environment Architecture Book II v2.02
26 - PowerPC Operating Environment Architecture Book III v2.02
27 PPC970 - PowerPC User Instruction Set Architecture Book I v2.01
28 - PowerPC Virtual Environment Architecture Book II v2.01
29 - PowerPC Operating Environment Architecture Book III v2.01
31 Power4+ - PowerPC User Instruction Set Architecture Book I v2.01
32 - PowerPC Virtual Environment Architecture Book II v2.01
33 - PowerPC Operating Environment Architecture Book III v2.01
[all …]
|
| D | elf_hwcaps.rst | 67 HWCAPs are allocated as described in Power Architecture 64-Bit ELF V2 ABI
130 The processor implements the embedded category ("BookE") architecture.
146 The processor supports the v2.05 userlevel architecture. Processors
159 The processor supports the v2.06 userlevel architecture. Processors
181 The processor supports the v2.07 userlevel architecture. Processors
208 The processor supports the v3.0B / v3.0C userlevel architecture. Processors
227 The processor supports the v3.1 userlevel architecture. Processors
|
| /Linux-v6.1/arch/ |
| D | Kconfig | 3 # General architecture dependent options
12 menu "General architecture-dependent options"
30 Select if the architecture can check permissions at sub-page
128 This symbol should be selected by an architecture if 64 bit
130 though it is not a 64 bit architecture.
144 This symbol should be selected by an architecture if it can
159 inline assembler that the architecture code provides in the
164 store-and-swap instructions if the architecture has them. It
169 Any architecture with load-and-swap or store-and-swap
210 of correct one. If the architecture stacktrace code and
[all …]
|
| /Linux-v6.1/arch/s390/crypto/ |
| D | Kconfig | 13 Architecture: s390
24 Architecture: s390
35 Architecture: s390
46 Architecture: s390
57 Architecture: s390
68 Architecture: s390
79 Architecture: s390
93 Architecture: s390
117 Architecture: s390
131 Architecture: s390
|
| /Linux-v6.1/include/linux/ |
| D | entry-common.h | 14 * Define dummy _TIF work flags if not defined by the architecture or for
66 * arch_enter_from_user_mode - Architecture specific sanity check for user mode regs
69 * Defaults to an empty implementation. Can be replaced by architecture
92 * Invoked from architecture specific syscall entry code with interrupts
97 * This is invoked when there is architecture specific functionality to be
107 * Invoked from architecture specific syscall entry code with interrupts
115 * This is invoked when there is extra architecture specific functionality
126 * Invoked from architecture specific syscall entry code with interrupts
128 * architecture specific work.
151 * Invoked from architecture specific syscall entry code with interrupts
[all …]
|
| D | kgdb.h | 34 * This can be implemented in the architecture specific portion of kgdb.
45 * This will be implemented as a static inline per architecture. This
46 * function is called by the kgdb core to execute an architecture
104 * Functions each KGDB-supporting architecture must provide:
108 * kgdb_arch_init - Perform any architecture specific initialization.
110 * This function will handle the initialization of any architecture
116 * kgdb_arch_exit - Perform any architecture specific uninitalization.
118 * This function will handle the uninitalization of any architecture
159 * kgdb_arch_handle_exception - Handle architecture specific GDB packets.
181 * kgdb_arch_handle_qxfer_pkt - Handle architecture specific GDB XML
[all …]
|
| /Linux-v6.1/arch/sparc/crypto/ |
| D | Kconfig | 17 Architecture: sparc64
27 Architecture: sparc64
37 Architecture: sparc64 using crypto instructions, when available
47 Architecture: sparc64
57 Architecture: sparc64 using crypto instructions, when available
67 Architecture: sparc64 using crypto instructions, when available
77 Architecture: sparc64 using crypto instructions
88 Architecture: sparc64
|
| /Linux-v6.1/drivers/watchdog/ |
| D | Makefile | 18 # watchdog-cards first, then the architecture specific watchdog
19 # drivers and then the architecture independent "softdog" driver.
21 # you can fall back to an architecture specific driver and if
37 # ALPHA Architecture
39 # ARM Architecture
102 # X86 (i386 + ia64 + x86_64) Architecture
154 # M68K Architecture
157 # MicroBlaze Architecture
160 # MIPS Architecture
181 # PARISC Architecture
[all …]
|
| /Linux-v6.1/arch/mips/crypto/ |
| D | Kconfig | 12 Architecture: mips
21 Architecture: mips
31 Architecture: mips OCTEON using crypto instructions, when available
41 Architecture: mips OCTEON
51 Architecture: mips OCTEON using crypto instructions, when available
61 Architecture: mips OCTEON using crypto instructions, when available
72 Architecture: MIPS32r2
|
| /Linux-v6.1/arch/powerpc/crypto/ |
| D | Kconfig | 13 Architecture: powerpc64 using
25 Architecture: powerpc64 using
45 Architecture: powerpc
53 Architecture: powerpc
61 Architecture: powerpc using
72 Architecture: powerpc using
83 Architecture: powerpc using:
94 architecture specific assembler implementations that work on 1KB
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 103 ARM ARM architecture is enabled.
104 ARM64 ARM64 architecture is enabled.
119 IA-64 IA-64 architecture is enabled.
120 IMA Integrity measurement architecture is enabled.
132 M68k M68k architecture is enabled.
136 MIPS MIPS architecture is enabled.
146 PARISC The PA-RISC architecture is enabled.
151 PPC PowerPC architecture is enabled.
155 RISCV RISCV architecture is enabled.
157 S390 S390 architecture is enabled.
[all …]
|
| /Linux-v6.1/Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 45 2. Architecture(s)
52 :Architecture: x86
60 :Architecture: x86
68 :Architecture: PPC
79 :Architecture: PPC
89 :Architecture: x86
105 :Architecture: x86
143 :Architecture: x86
164 :Architecture: x86
175 :Architecture: x86
|
| /Linux-v6.1/Documentation/mm/ |
| D | memory-model.rst | 18 FLATMEM and SPARSEMEM. Each architecture defines what
45 To allocate the `mem_map` array, architecture specific setup code should
50 An architecture may free parts of the `mem_map` array that do not cover the
51 actual physical pages. In such case, the architecture specific
77 `MAX_PHYSMEM_BITS` constants defined by each architecture that
79 physical address that an architecture supports, the
102 The architecture setup code should call sparse_init() to
121 To use vmemmap, an architecture has to reserve a range of virtual
124 the architecture should implement :c:func:`vmemmap_populate` method
126 virtual memory map. If an architecture does not have any special
|
| /Linux-v6.1/tools/perf/pmu-events/ |
| D | README | 19 - To reduce JSON event duplication per architecture, platform JSONs may
20 use "ArchStdEvent" keyword to dereference an "Architecture standard
21 events", defined in architecture standard JSONs.
22 Architecture standard JSONs must be located in the architecture root
44 - Set of 'PMU events tables' for all known CPUs in the architecture,
61 - A 'mapping table' that maps each CPU of the architecture, to its
86 3. _All_ known CPU tables for architecture are included in the perf
|
| /Linux-v6.1/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cpus.txt | 2 Power Architecture CPU Binding
5 Power Architecture CPUs in Freescale SOCs are represented in device trees as
17 Freescale Power Architecture) defines the architecture for Freescale
18 Power CPUs. The EREF defines some architecture categories not defined
|
| /Linux-v6.1/Documentation/features/ |
| D | arch-support.txt | 2 For generic kernel features that need architecture support, the
8 | ok | # feature supported by the architecture
9 |TODO| # feature not yet supported by the architecture
11 | N/A| # feature doesn't apply to the architecture
|
| /Linux-v6.1/scripts/package/ |
| D | mkdebian | 27 # Attempt to find the correct Debian architecture
75 debarch=$(dpkg-architecture -qDEB_HOST_ARCH)
79 echo "Your architecture doesn't have its equivalent" >&2
80 echo "Debian userspace architecture defined!" >&2
81 echo "Falling back to the current host architecture ($debarch)." >&2
182 Architecture: $debarch
190 Architecture: $debarch
201 Architecture: $debarch
214 Architecture: $debarch
|
| /Linux-v6.1/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
19 Architecture support for this is certainly not in the "trivial"
21 state changes. But an architecture can be irq-flags-tracing enabled in a
42 - if the architecture has non-maskable interrupts then those need to be
47 implementation in an architecture: lockdep will detect that and will
|
| /Linux-v6.1/include/asm-generic/ |
| D | tlb.h | 111 * And allows the architecture to provide and implement tlb_flush():
129 * If an architecture does not provide tlb_flush() a default implementation
140 * This might be useful if your architecture has size specific TLB
148 * Useful if your architecture has non-page page directories.
150 * When used, an architecture is expected to provide __tlb_remove_table()
158 * Useful if your architecture doesn't use IPIs for remote TLB invalidates
163 * Indicates the architecture has flush_cache_range() but it needs *NOT* be called
172 * Indicates the architecture wants to merge ranges over VMAs; typical when
177 * Use this if your architecture lacks an efficient flush_tlb_range(). This
187 * This is useful if your architecture already flushes TLB entries in the
[all …]
|
| /Linux-v6.1/Documentation/timers/ |
| D | highres.rst | 48 code out of the architecture-specific areas into a generic management
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
76 for various event driven functionalities is hardwired into the architecture
80 architecture. Another implication of the current design is that it is necessary
81 to touch all the architecture-specific implementations in order to provide new
87 to minimize the clock event related architecture dependent code to the pure
93 Clock event devices are registered either by the architecture dependent boot
116 architecture specific timer interrupt handlers and hands the control over the
131 The conversion of an architecture has no functional impact, but allows to
135 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
|
| /Linux-v6.1/tools/include/nolibc/ |
| D | nolibc.h | 22 * - The second level is mostly architecture-independent. It is made of
27 * A few of them are architecture-specific because the syscalls are not all
51 * structures like the sys_stat struct depend on the architecture.
53 * The definitions start with the architecture-specific parts, which are picked
54 * based on what the compiler knows about the target architecture, and are
56 * target architecture, cross-compiling normally works out of the box without
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 29 socket number, but the actual value is architecture and platform
36 architecture and platform dependent.
42 architecture and platform dependent.
48 architecture and platform dependent.
54 architecture and platform dependent. it's only used on s390.
60 architecture and platform dependent. it's only used on s390.
|
12345678910>>...76
