Searched refs:architecture (Results 1 – 25 of 461) sorted by relevance
12345678910>>...19
/linux-6.1.9/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-6.1.9/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-6.1.9/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-6.1.9/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-6.1.9/Documentation/x86/x86_64/ |
D | machinecheck.rst | 29 For more details about the x86 machine check architecture 30 see the Intel and AMD architecture manuals from their developer websites. 32 For more details about the architecture
|
/linux-6.1.9/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-6.1.9/Documentation/core-api/irq/ |
D | irqflags-tracing.rst | 15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these 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-6.1.9/Documentation/ABI/stable/ |
D | syscalls | 7 Note that this interface is different for every architecture 8 that Linux supports. Please see the architecture-specific
|
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.
|
/linux-6.1.9/Documentation/usb/ |
D | linux.inf | 19 ; Decoration for x86 architecture 23 ; Decoration for x64 architecture 27 ; Decoration for ia64 architecture
|
/linux-6.1.9/tools/perf/pmu-events/ |
D | README | 19 - To reduce JSON event duplication per architecture, platform JSONs may 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-6.1.9/Documentation/arm64/ |
D | legacy_instructions.rst | 7 the architecture. The infrastructure code uses undefined instruction 19 have been obsoleted in the architecture, e.g., SWP 39 architecture. Deprecated instructions should default to emulation
|
D | amu.rst | 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-6.1.9/lib/crypto/ |
D | Kconfig | 17 Declares whether the architecture provides an arch-specific 33 Declares whether the architecture provides an arch-specific 59 Declares whether the architecture provides an arch-specific 95 Declares whether the architecture provides an arch-specific
|
/linux-6.1.9/Documentation/nios2/ |
D | nios2.rst | 2 Linux on the Nios II architecture 17 Nios II is a 32-bit embedded-processor architecture designed specifically for the
|
/linux-6.1.9/Documentation/arm/samsung/ |
D | gpio.rst | 8 This outlines the Samsung GPIO implementation and the architecture 33 Pin configuration is specific to the Samsung architecture, with each SoC
|
/linux-6.1.9/Documentation/devicetree/bindings/nvmem/ |
D | fsl,layerscape-sfp.yaml | 22 - description: Trust architecture 2.1 SFP 25 - description: Trust architecture 3.0 SFP
|
/linux-6.1.9/drivers/clk/bcm/ |
D | Kconfig | 30 based on the ARM architecture 38 based on the MIPS architecture 53 based on the iProc architecture
|
/linux-6.1.9/Documentation/dev-tools/kunit/ |
D | index.rst | 12 architecture 57 - Runs tests on any kernel architecture. 104 * Documentation/dev-tools/kunit/architecture.rst - KUnit architecture.
|
/linux-6.1.9/Documentation/powerpc/ |
D | elf_hwcaps.rst | 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-6.1.9/Documentation/devicetree/bindings/arm/ti/ |
D | k3.yaml | 7 title: Texas Instruments K3 Multicore SoC architecture device tree bindings 13 Platforms based on Texas Instruments K3 Multicore SoC architecture
|
/linux-6.1.9/Documentation/core-api/ |
D | genericirq.rst | 22 interrupt subsystem based for their architecture, with the help of the 67 Analysing a couple of architecture's IRQ subsystem implementations 81 and extensible. For example, an (sub)architecture can use a generic 83 (sub)architecture specific 'edge type' implementation. 118 Whenever an interrupt triggers, the low-level architecture code calls 173 The interrupt flow handlers (either pre-defined or architecture 174 specific) are assigned to specific interrupts by the architecture either 321 which have no platform-specific IRQ handling quirks. If an architecture 385 The locking of chip registers is up to the architecture that defines the
|
/linux-6.1.9/Documentation/devicetree/bindings/powerpc/fsl/ |
D | cpus.txt | 17 Freescale Power Architecture) defines the architecture for Freescale 18 Power CPUs. The EREF defines some architecture categories not defined
|
/linux-6.1.9/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-6.1.9/Documentation/ABI/testing/ |
D | sysfs-mce | 12 For more details about the x86 machine check architecture 13 see the Intel and AMD architecture manuals from their 16 For more details about the architecture
|
12345678910>>...19