Searched full:architecture (Results 1 – 25 of 2921) sorted by relevance
12345678910>>...117
| /kernel/liteos_m/ |
| D | arch_spec.md | 3 … --- Code of the kernel instruction architecture layer 4 │ ├── arm --- ARM32 architecture 5 │ │ ├── arm9 --- ARM9 architecture 7 │ │ ├── cortex-m3 --- Cortex-m3 architecture 9 │ │ ├── cortex-m33 --- Cortex-m33 architecture 11 … │ │ │── NTZ --- Cortex-m33 Non-TrustZone architecture 12 … │ │ │ └── TZ --- Cortex-m33 TrustZone architecture 14 … │ │── NTZ --- Cortex-m33 Non-TrustZone architecture 15 … │ │ └── TZ --- Cortex-m33 TrustZone architecture 16 │ │ └── cortex-m4 --- Cortex-m4 architecture [all …]
|
| D | README.md | 13 **Figure1** shows the architecture of the LiteOS-M kernel. 15 **Figure 1** Architecture of the OpenHarmony LiteOS-M kernel<a name="fig0865152210223"></a> 17 . Can be supplied by architecture specific [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 initalization. 110 * This function will handle the initalization 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 …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | kgdb.h | 33 * This can be implemented in the architecture specific portion of kgdb. 44 * This will be implemented as a static inline per architecture. This 45 * function is called by the kgdb core to execute an architecture 103 * Functions each KGDB-supporting architecture must provide: 107 * kgdb_arch_init - Perform any architecture specific initalization. 109 * This function will handle the initalization of any architecture 115 * kgdb_arch_exit - Perform any architecture specific uninitalization. 117 * This function will handle the uninitalization of any architecture 158 * kgdb_arch_handle_exception - Handle architecture specific GDB packets. 203 * architecture specific implementation. [all …]
|
| /kernel/linux/linux-4.19/arch/ |
| D | Kconfig | 3 # General architecture dependent options 12 menu "General architecture-dependent options" 140 This symbol should be selected by an architecture if 64 bit 142 though it is not a 64 bit architecture. 156 This symbol should be selected by an architecture if it can 171 inline assembler that the architecture code provides in the 176 store-and-swap instructions if the architecture has them. It 181 Any architecture with load-and-swap or store-and-swap 245 An architecture should select this when it can successfully 264 An architecture should select this to provide hardened usercopy [all …]
|
| /kernel/linux/linux-4.19/drivers/watchdog/ |
| D | Makefile | 17 # watchdog-cards first, then the architecture specific watchdog 18 # drivers and then the architecture independent "softdog" driver. 20 # you can fall back to an architecture specific driver and if 36 # ALPHA Architecture 38 # ARM Architecture 95 # X86 (i386 + ia64 + x86_64) Architecture 143 # M68K Architecture 146 # MicroBlaze Architecture 149 # MIPS Architecture 171 # PARISC Architecture [all …]
|
| /kernel/linux/linux-5.10/drivers/watchdog/ |
| D | Makefile | 17 # watchdog-cards first, then the architecture specific watchdog 18 # drivers and then the architecture independent "softdog" driver. 20 # you can fall back to an architecture specific driver and if 36 # ALPHA Architecture 38 # ARM Architecture 100 # X86 (i386 + ia64 + x86_64) Architecture 150 # M68K Architecture 153 # MicroBlaze Architecture 156 # MIPS Architecture 178 # PARISC Architecture [all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 90 ARM ARM architecture is enabled. 91 ARM64 ARM64 architecture is enabled. 105 IA-64 IA-64 architecture is enabled. 106 IMA Integrity measurement architecture is enabled. 119 M68k M68k architecture is enabled. 123 MIPS MIPS architecture is enabled. 134 PARISC The PA-RISC architecture is enabled. 139 PPC PowerPC architecture is enabled. 144 S390 S390 architecture is enabled. 152 SH SuperH architecture is enabled. [all …]
|
| D | cputopology.rst | 12 socket number, but the actual value is architecture and platform 19 architecture and platform dependent. 25 architecture and platform dependent. 31 architecture and platform dependent. 37 architecture and platform dependent. 87 Architecture-neutral, drivers/base/topology.c, exports these attributes. 94 For an architecture to support this feature, it must define some of
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 90 ARM ARM architecture is enabled. 104 IA-64 IA-64 architecture is enabled. 105 IMA Integrity measurement architecture is enabled. 118 M68k M68k architecture is enabled. 122 MIPS MIPS architecture is enabled. 132 PARISC The PA-RISC architecture is enabled. 137 PPC PowerPC architecture is enabled. 142 S390 S390 architecture is enabled. 150 SH SuperH architecture is enabled. 152 SPARC Sparc architecture is enabled. [all …]
|
| /kernel/linux/linux-5.10/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")
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/ |
| D | hypercalls.txt | 40 2. Architecture(s) 46 Architecture: x86 53 Architecture: x86 60 Architecture: PPC 69 Architecture: PPC 78 Architecture: x86 93 Architecture: x86 127 Architecture: x86
|
| /kernel/linux/linux-4.19/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 177 Architecture: $debarch 183 Architecture: $debarch 192 Architecture: $debarch 199 Architecture: $debarch
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | memory-model.rst | 18 FLATMEM, DISCONTIGMEM and SPARSEMEM. Each architecture defines what 49 To allocate the `mem_map` array, architecture specific setup code should 54 If an architecture enables `CONFIG_ARCH_HAS_HOLES_MEMORYMODEL` option, 56 actual physical pages. In such case, the architecture specific 79 The architecture setup code should call :c:func:`free_area_init_node` for 119 `MAX_PHYSMEM_BITS` constants defined by each architecture that 121 physical address that an architecture supports, the 144 The architecture setup code should call sparse_init() to 163 To use vmemmap, an architecture has to reserve a range of virtual 166 the architecture should implement :c:func:`vmemmap_populate` method [all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | irqflags-tracing.txt | 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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/s390/ |
| D | Debugging390.txt | 2 Debugging on Linux for s/390 & z/Architecture 11 s/390 and z/Architecture. It is not intended as a complete reference and not a 16 It is intended like the Enterprise Systems Architecture/390 Reference Summary 24 Address Spaces on Linux for s/390 & z/Architecture 25 The Linux for s/390 & z/Architecture Kernel Task Structure 26 Register Usage & Stackframes on Linux for s/390 & z/Architecture 28 Compiling programs for debugging on Linux for s/390 & z/Architecture 30 s/390 & z/Architecture IO Overview 31 Debugging IO on s/390 & z/Architecture under VM 32 GDB on s/390 & z/Architecture [all …]
|
12345678910>>...117