Searched full:architecture (Results 1 – 25 of 1769) sorted by relevance
12345678910>>...71
/Linux-v5.15/include/linux/ |
D | entry-common.h | 14 * Define dummy _TIF work flags if not defined by the architecture or for 66 * arch_check_user_regs - Architecture specific sanity check for user mode regs 69 * Defaults to an empty implementation. Can be replaced by architecture 89 * architecture specific code. 112 * Invoked from architecture specific syscall entry code with interrupts 117 * This is invoked when there is architecture specific functionality to be 127 * Invoked from architecture specific syscall entry code with interrupts 135 * This is invoked when there is extra architecture specific functionality 146 * Invoked from architecture specific syscall entry code with interrupts 148 * architecture specific work. [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-v5.15/arch/ |
D | Kconfig | 3 # General architecture dependent options 12 menu "General architecture-dependent options" 123 This symbol should be selected by an architecture if 64 bit 125 though it is not a 64 bit architecture. 139 This symbol should be selected by an architecture if it can 154 inline assembler that the architecture code provides in the 159 store-and-swap instructions if the architecture has them. It 164 Any architecture with load-and-swap or store-and-swap 231 An architecture should select this when it can successfully 250 # Select if the architecture provides the arch_dma_set_uncached symbol to [all …]
|
/Linux-v5.15/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 98 # X86 (i386 + ia64 + x86_64) Architecture 148 # M68K Architecture 151 # MicroBlaze Architecture 154 # MIPS Architecture 175 # PARISC Architecture [all …]
|
/Linux-v5.15/Documentation/admin-guide/ |
D | kernel-parameters.rst | 102 ARM ARM architecture is enabled. 103 ARM64 ARM64 architecture is enabled. 117 IA-64 IA-64 architecture is enabled. 118 IMA Integrity measurement architecture is enabled. 131 M68k M68k architecture is enabled. 135 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-v5.15/Documentation/powerpc/ |
D | isa-versions.rst | 8 CPU Architecture version 20 Power5 - PowerPC User Instruction Set Architecture Book I v2.02 21 - PowerPC Virtual Environment Architecture Book II v2.02 22 - PowerPC Operating Environment Architecture Book III v2.02 23 PPC970 - PowerPC User Instruction Set Architecture Book I v2.01 24 - PowerPC Virtual Environment Architecture Book II v2.01 25 - PowerPC Operating Environment Architecture Book III v2.01 68 …e Power ISA v3.1, "Appendix A. Notes on the Removal of Transactional Memory from the Architecture")
|
/Linux-v5.15/Documentation/virt/kvm/ |
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-v5.15/Documentation/vm/ |
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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/drivers/infiniband/ulp/srpt/ |
D | ib_dm_mad.h | 45 * InfiniBand Architecture Specification. 55 * Architecture Specification. 87 * Architecture Specification. 98 * the InfiniBand Architecture Specification. 132 * See also section 16.3.3.5 ServiceEntries in the InfiniBand Architecture
|
/Linux-v5.15/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 * Use this if your architecture lacks an efficient flush_tlb_range(). 172 * This is useful if your architecture already flushes TLB entries in the 194 * Without MMU_GATHER_TABLE_FREE the architecture is assumed to have page based 203 * This allows an architecture that does not use the linux page-tables for [all …]
|
/Linux-v5.15/Documentation/arm64/ |
D | amu.rst | 15 Architecture overview 19 ARMv8.4 CPU architecture. 26 Version 1 of the Activity Monitors architecture implements a counter group 39 The Activity Monitors architecture provides space for up to 16 architected 40 event counters. Future versions of the architecture may use this space to
|
/Linux-v5.15/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. it's only used on s390. 54 architecture and platform dependent. it's only used on s390.
|
/Linux-v5.15/tools/memory-model/Documentation/ |
D | references.txt | 9 o SPARC International Inc. (Ed.). 1994. "The SPARC Architecture 12 o Compaq Computer Corporation (Ed.). 2002. "Alpha Architecture 44 o ARM Ltd. (Ed.). 2014. "ARM Architecture Reference Manual (ARMv8, 45 for ARMv8-A architecture profile)". ARM Ltd. 47 o Imagination Technologies, LTD. 2015. "MIPS(R) Architecture 54 Sewell. 2016. "Modelling the ARMv8 Architecture, Operationally:
|
/Linux-v5.15/lib/crypto/ |
D | Kconfig | 14 Declares whether the architecture provides an arch-specific 39 Declares whether the architecture provides an arch-specific 65 Declares whether the architecture provides an arch-specific 100 Declares whether the architecture provides an arch-specific
|
/Linux-v5.15/tools/power/cpupower/man/ |
D | cpupower-idle-info.1 | 33 processor. This often is the case on the X86 architecture when the acpi_idle 39 state residencies. Please refer to the architecture specific description 42 .SH IDLE\-INFO ARCHITECTURE SPECIFIC DESCRIPTIONS 53 There exist two different cpuidle drivers on the X86 architecture platform:
|
/Linux-v5.15/arch/mips/jazz/ |
D | Kconfig | 9 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at 20 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at 30 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
/Linux-v5.15/scripts/ |
D | get_feat.pl | 78 my $h_arch = "Architecture"; 188 parse_error($file, $ln, "Architecture table not found", ""); 203 # Output feature(s) for a given architecture 206 my $title = "Feature status on $arch architecture"; 265 # list feature(s) for a given architecture 268 print "#\n# Kernel feature support matrix of the '$arch' architecture:\n#\n"; 419 printf "|%-${status_size}s|\n", "Status per architecture"; 550 with features for this machine's architecture 559 B<ls> or B<list> - list features for this machine's architecture, 571 Output features for an specific architecture, optionally filtering for [all …]
|
/Linux-v5.15/arch/arm64/include/asm/ |
D | kgdb.h | 45 * Architecture Reference Manual that claimed "SPSR_ELx is a 32-bit register". 51 * RES0.". RES0 is heavily used in the ARM architecture documents as a 52 * way to leave space for future architecture changes. So to translate a 53 * little for people who don't spend their spare time reading ARM architecture
|
/Linux-v5.15/Documentation/kbuild/ |
D | makefiles.rst | 43 === 7 Architecture Makefiles 44 --- 7.1 Set variables to tweak the build to the architecture 48 --- 7.5 Architecture-specific boot images 88 architecture-specific information to the top Makefile. 115 *Arch developers* are people who work on an entire architecture, such 493 Another example are the architecture-specific Makefiles which 709 This functionality is useful for architecture Makefiles that try 913 for the target architecture (i.e. the same architecture as you are building 923 built for the target architecture. 1042 but in the architecture makefiles where the kbuild infrastructure [all …]
|
12345678910>>...71