/linux/arch/x86/crypto/ |
H A D | Kconfig | 13 Architecture: x86_64 using: 30 Architecture: x86 (32-bit and 64-bit) using: 47 Architecture: x86_64 58 Architecture: x86_64 70 Architecture: x86_64 using: 81 Architecture: x86_64 using: 97 Architecture: x86_64 using: 115 Architecture: x86_64 using: 130 Architecture: x86_64 145 Architecture: x86_64 using: [all …]
|
/linux/arch/arm64/crypto/ |
H A 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/arch/arm/crypto/ |
H A D | Kconfig | 13 Architecture: arm with 27 Architecture: arm using 44 Architecture: arm using: 54 Architecture: arm optionally using 63 Architecture: arm 77 Architecture: arm using 93 Architecture: arm 104 Architecture: arm using 115 Architecture: arm using ARMv8 Crypto Extensions 125 Architecture: arm using [all …]
|
/linux/Documentation/arch/powerpc/ |
H A 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 …]
|
H A D | elf_hwcaps.rst | 67 HWCAPs are allocated as described in Power Architecture 64-Bit ELF V2 ABI 131 The processor implements the embedded category ("BookE") architecture. 147 The processor supports the v2.05 userlevel architecture. Processors 160 The processor supports the v2.06 userlevel architecture. Processors 182 The processor supports the v2.07 userlevel architecture. Processors 209 The processor supports the v3.0B / v3.0C userlevel architecture. Processors 228 The processor supports the v3.1 userlevel architecture. Processors
|
/linux/arch/s390/crypto/ |
H A D | Kconfig | 12 Architecture: s390 23 Architecture: s390 34 Architecture: s390 45 Architecture: s390 56 Architecture: s390 67 Architecture: s390 81 Architecture: s390 105 Architecture: s390 119 Architecture: s390 131 Architecture: s390
|
/linux/include/linux/ |
H A 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 specifi [all...] |
H A D | entry-common.h | 19 * Define dummy _TIF work flags if not defined by the architecture or for 72 * arch_enter_from_user_mode - Architecture specific sanity check for user mode regs 75 * Defaults to an empty implementation. Can be replaced by architecture 98 * Invoked from architecture specific syscall entry code with interrupts 103 * This is invoked when there is architecture specific functionality to be 125 * Invoked from architecture specific syscall entry code with interrupts 133 * This is invoked when there is extra architecture specific functionality 147 * Invoked from architecture specific syscall entry code with interrupts 149 * architecture specific work. 180 * Invoked from architecture specific syscall entry code with interrupts [all …]
|
/linux/drivers/watchdog/ |
H A 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 105 # X86 (i386 + ia64 + x86_64) Architecture 159 # M68K Architecture 162 # MicroBlaze Architecture 166 # MIPS Architecture 186 # PARISC Architecture [all …]
|
/linux/arch/powerpc/crypto/ |
H A D | Kconfig | 13 Architecture: PowerPC64 23 Architecture: powerpc 31 Architecture: powerpc 39 Architecture: powerpc using 50 Architecture: powerpc using 61 Architecture: powerpc using: 72 architecture specific assembler implementations that work on 1KB 86 Architecture: powerpc64 using: 103 Architecture: PowerPC64 115 Architecture: PowerPC64
|
/linux/drivers/perf/arm_cspmu/ |
H A D | Kconfig | 6 tristate "ARM Coresight Architecture PMU" 10 based on ARM CoreSight PMU architecture. Note that this PMU 11 architecture does not have relationship with the ARM CoreSight 15 tristate "NVIDIA Coresight Architecture PMU" 19 (PMU) devices based on ARM CoreSight PMU architecture. 22 tristate "Ampere Coresight Architecture PMU" 26 (PMU) devices based on ARM CoreSight PMU architecture.
|
/linux/arch/sparc/crypto/ |
H A D | Kconfig | 17 Architecture: sparc64 27 Architecture: sparc64 using crypto instructions, when available 37 Architecture: sparc64 47 Architecture: sparc64 using crypto instructions, when available 57 Architecture: sparc64 using crypto instructions, when available 67 Architecture: sparc64 using crypto instructions 78 Architecture: sparc64
|
/linux/arch/riscv/crypto/ |
H A D | Kconfig | 15 Architecture: riscv64 using: 29 Architecture: riscv64 using: 39 Architecture: riscv64 using: 49 Architecture: riscv64 using: 60 Architecture: riscv64 using: 72 Architecture: riscv64 using: 89 Architecture: riscv64 using:
|
/linux/arch/mips/crypto/ |
H A D | Kconfig | 12 Architecture: mips 22 Architecture: mips OCTEON using crypto instructions, when available 32 Architecture: mips OCTEON 42 Architecture: mips OCTEON using crypto instructions, when available 52 Architecture: mips OCTEON using crypto instructions, when available 63 Architecture: MIPS32r2
|
/linux/Documentation/mm/ |
H A D | memory-model.rst | 16 FLATMEM and SPARSEMEM. Each architecture defines what 43 To allocate the `mem_map` array, architecture specific setup code should 48 An architecture may free parts of the `mem_map` array that do not cover the 49 actual physical pages. In such case, the architecture specific 75 `MAX_PHYSMEM_BITS` constants defined by each architecture that 77 physical address that an architecture supports, the 100 The architecture setup code should call sparse_init() to 119 To use vmemmap, an architecture has to reserve a range of virtual 122 the architecture should implement :c:func:`vmemmap_populate` method 124 virtual memory map. If an architecture does not have any special
|
/linux/Documentation/virt/kvm/x86/ |
H A 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/scripts/package/ |
H A D | mkdebian | 27 # Attempt to find the correct Debian architecture 82 debarch=$(dpkg-architecture -qDEB_HOST_ARCH) 86 echo "Your architecture doesn't have its equivalent" >&2 87 echo "Debian userspace architecture defined!" >&2 88 echo "Falling back to the current host architecture ($debarch)." >&2 189 host_gnu=$(dpkg-architecture -a "${debarch}" -q DEB_HOST_GNU_TYPE | sed 's/_/-/g') 216 Architecture: $debarch 228 Architecture: $debarch 239 Architecture: $debarch 254 Architecture: $debarch
|
/linux/tools/perf/pmu-events/ |
H A 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/Documentation/devicetree/bindings/powerpc/fsl/ |
H A 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/Documentation/features/ |
H A 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/Documentation/core-api/irq/ |
H A 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/include/asm-generic/ |
H A D | tlb.h | 117 * And allows the architecture to provide and implement tlb_flush(): 135 * If an architecture does not provide tlb_flush() a default implementation 146 * This might be useful if your architecture has size specific TLB 154 * Useful if your architecture has non-page page directories. 156 * When used, an architecture is expected to provide __tlb_remove_table() or 165 * Useful if your architecture doesn't use IPIs for remote TLB invalidates 170 * Indicates the architecture has flush_cache_range() but it needs *NOT* be called 179 * Indicates the architecture wants to merge ranges over VMAs; typical when 184 * Use this if your architecture lacks an efficient flush_tlb_range(). This 194 * This is useful if your architecture alread [all...] |
H A D | ticket_spinlock.h | 7 * guarantees under contention. If your architecture cannot provide this, stick 12 * you'd be hard pressed to find anything useful in architecture specifications 13 * about this. If your architecture cannot do this you might be better off with 22 * architecture has WFE like instructions to sleep instead of poll for word 94 * Remapping spinlock architecture specific functions to the corresponding
|
/linux/Documentation/timers/ |
H A 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/Documentation/ABI/stable/ |
H A 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.
|