Searched full:architecture (Results 1 – 25 of 346) sorted by relevance
12345678910>>...14
| /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
|
| /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
|
| D | list-arch.sh | 3 # of an architecture.
5 # (If no arguments are given then it will print the host architecture's status.)
12 echo "# Kernel feature support matrix of the '$ARCH' architecture:"
|
| /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")
|
| D | associativity.rst | 17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
57 "ibm,architecture-vec-5" property.
|
| /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
|
| /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
|
| /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
|
| /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 An architecture may free parts of the `mem_map` array that do not cover the
55 actual physical pages. In such case, the architecture specific
78 The architecture setup code should call :c:func:`free_area_init_node` for
118 `MAX_PHYSMEM_BITS` constants defined by each architecture that
120 physical address that an architecture supports, the
143 The architecture setup code should call sparse_init() to
162 To use vmemmap, an architecture has to reserve a range of virtual
165 the architecture should implement :c:func:`vmemmap_populate` method
[all …]
|
| /Documentation/ABI/stable/ |
| D | syscalls | 7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
|
| /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
|
| 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 | tagged-pointers.rst | 63 Due to architecture limitations, bits 63:60 of the fault address
67 future architecture revisions which may preserve the bits.
76 The architecture prevents the use of a tagged PC, so the upper byte will
|
| /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
|
| /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
|
| D | timekeeping.rst | 10 If you grep through the kernel source you will find a number of architecture-
12 architecture-specific overrides of the sched_clock() function and some
113 number of nanoseconds since the system was started. An architecture may or
133 If an architecture does not provide its own implementation of this function,
135 jiffy frequency for the architecture. This will affect scheduling accuracy
148 architecture, special helper functions have been created to provide a
|
| /Documentation/usb/ |
| D | linux.inf | 19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | sbsa-gwdt.txt | 1 * SBSA (Server Base System Architecture) Generic Watchdog
6 Base System Architecture (SBSA)
|
| /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
|
| /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
|
| /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
|
| /Documentation/scsi/ |
| D | ufs.rst | 11 2. UFS Architecture Overview
50 2. UFS Architecture Overview
53 UFS has a layered communication architecture which is based on SCSI
56 UFS communication architecture consists of following layers,
101 UIC is the lowest layer of UFS layered architecture. It handles
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 81 For more details about the x86 machine check architecture
82 see the Intel and AMD architecture manuals from their developer websites.
84 For more details about the architecture
|
| /Documentation/kbuild/ |
| D | makefiles.rst | 41 === 7 Architecture Makefiles
42 --- 7.1 Set variables to tweak the build to the architecture
46 --- 7.5 Architecture-specific boot images
86 architecture-specific information to the top Makefile.
113 *Arch developers* are people who work on an entire architecture, such
431 Another example are the architecture-specific Makefiles which
579 This functionality is useful for architecture Makefiles that try
783 for the target architecture (i.e. the same architecture as you are building
793 built for the target architecture.
914 but in the architecture makefiles where the kbuild infrastructure
[all …]
|
12345678910>>...14