| /linux-4.1.27/Documentation/ |
| D | irqflags-tracing.txt | 13 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
17 architecture support for this is certainly not in the "trivial"
19 state changes. But an architecture can be irq-flags-tracing enabled in a
40 - if the architecture has non-maskable interrupts then those need to be
45 implementation in an architecture: lockdep will detect that and will
|
| D | cputopology.txt | 8 socket number, but the actual value is architecture and platform
15 architecture and platform dependent.
21 architecture and platform dependent.
38 To implement it in an architecture-neutral way, a new source file,
42 For an architecture to support this feature, it must define some of
|
| D | 00-INDEX | 77 - directory with info about Linux on the ARM architecture.
79 - directory with info about Linux on the 64 bit ARM architecture.
141 - directory with info about Linux on CRIS architecture.
223 - directory with info about Linux on Intel 32 bit architecture.
225 - directory with info about Linux on Intel 64 bit architecture.
299 - directory with info about Linux on Motorola 68k architecture.
315 - directory with info about Linux on Meta architecture.
317 - directory with info about Linux on MIPS architecture.
323 - directory with info about the mn10300 architecture port
347 - directory with info on using Linux on PA-RISC architecture.
[all …]
|
| D | local_ops.txt | 7 to implement them for any given architecture and shows how they can be used
38 * Implementation for a given architecture
42 i386 and x86_64) and any SMP synchronization barrier. If the architecture does
44 in your architecture's local.h is sufficient.
|
| D | IRQ.txt | 11 are architecture specific.
|
| D | kselftest.txt | 66 * Don't break the build on any architecture, and
|
| D | kernel-docs.txt | 79 Keywords: conceptual software architecture, extracted design,
81 Description: Conceptual software architecture of the Linux kernel,
88 Keywords: concrete architecture, extracted design, reverse
90 Description: Concrete architecture of the Linux kernel,
99 Keywords: software architecture, architecture recovery,
224 Gives the basic concepts on the architecture of the PCI subsystem,
324 sound architecture in the 2.6 kernel version.
|
| D | IRQ-domain.txt | 166 To support such a hardware topology and make software architecture match
167 hardware architecture, an irq_domain data structure is built for each
210 software architecture.
|
| D | unaligned-memory-access.txt | 34 When writing code, assume the target architecture has natural alignment
46 The effects of performing an unaligned memory access vary from architecture
47 to architecture. It would be easy to write a whole document on the differences
|
| D | init.txt | 29 E) make sure the binary's architecture matches your hardware.
|
| D | lockup-watchdogs.txt | 36 in principle, they should work in any architecture where these
|
| D | cachetlb.txt | 94 tell the architecture specific code that a translation
305 simply be defined as a nop on that architecture.
308 "architecture private". The kernel guarantees that,
320 page->mapping->i_mmap is an empty tree, just mark the architecture
|
| D | Intel-IOMMU.txt | 4 The architecture spec can be obtained from the below location.
|
| D | parport.txt | 13 port-sharing) and architecture-dependent (which deals with actually
25 architecture-dependent code with (for example):
|
| D | DMA-API-HOWTO.txt | 97 microprocessor architecture. You should use the DMA API rather than the
924 an architecture port for the kernel, you can safely skip down
929 Don't invent the architecture specific struct scatterlist; just use
931 CONFIG_NEED_SG_DMA_LENGTH if the architecture supports IOMMUs
937 DMA-safe. Drivers and subsystems depend on it. If an architecture
945 constraints. You don't need to worry about the architecture data
951 If your architecture needs to support multiple types of IOMMUs, you
|
| D | SubmitChecklist | 26 4: ppc64 is a good architecture for cross-compilation checking because it
|
| D | memory-hotplug.txt | 93 a memory section is architecture dependent. For example, power uses 16MiB, ia64
97 size of a memory block is architecture dependent and represents the logical
100 architecture specifies otherwise. (see Section 3.)
|
| D | ramoops.txt | 90 very early in the architecture code, e.g.:
|
| D | stable_api_nonsense.txt | 68 There is no way that binary drivers from one architecture will run
69 on another architecture properly.
|
| D | gdb-kernel-debugging.txt | 29 CONFIG_DEBUG_INFO_REDUCED off. If your architecture supports
|
| D | kprobes.txt | 394 architecture-specific trap number associated with the fault (e.g.,
445 the architecture's ABI.
560 architecture and optimization state, handlers may also run with
626 million hits per second, depending on the architecture. A jprobe or
|
| D | kasan.txt | 16 Currently KASan is supported only for x86_64 architecture and requires that the
|
| D | cpu-hotplug.txt | 366 Q: If i would like to develop cpu hotplug support for a new architecture,
381 architecture. __cpu_die() typically waits for some
|
| D | kernel-parameters.txt | 53 ARM ARM architecture is enabled.
54 AVR32 AVR32 architecture is enabled.
56 BLACKFIN Blackfin architecture is enabled.
69 IA-64 IA-64 architecture is enabled.
70 IMA Integrity measurement architecture is enabled.
82 M68k M68k architecture is enabled.
86 MIPS MIPS architecture is enabled.
96 PARISC The PA-RISC architecture is enabled.
101 PPC PowerPC architecture is enabled.
105 S390 S390 architecture is enabled.
[all …]
|
| D | parport-lowlevel.txt | 74 IEEE 1284-capable architecture.
1118 architecture-specific. For the PC architecture, interrupts are
|
| D | module-signing.txt | 160 Further, the architecture code may take public keys from a hardware store and
|
| D | DMA-API.txt | 402 The interpretation of DMA attributes is architecture-specific, and
587 violations. If your architecture supports it you can select the "Enable
690 of preallocated entries is defined per architecture. If it is too low for you
|
| D | HOWTO | 25 The kernel is written mostly in C, with some architecture-dependent
27 kernel development. Assembly (any architecture) is not required unless
28 you plan to do low-level development for that architecture. Though they
|
| D | static-keys.txt | 146 to take advantage of this optimization. If there is no architecture support, we
|
| D | printk-formats.txt | 17 blkcnt_t) or is architecture-dependent for its size (e.g., tcflag_t), use a
|
| /linux-4.1.27/Documentation/frv/ |
| D | README.txt | 5 This directory contains documentation for the Fujitsu FR-V CPU architecture
12 A description of the basic features inherent in this architecture port.
17 A summary of the configuration options particular to this architecture.
|
| D | configuring.txt | 44 There are some architecture specific configuration options in the "General
69 architecture. See the "gdbstub.txt" file for information about those.
|
| D | features.txt | 9 The FR-V architecture port supports both normal MMU linux and uClinux out
45 and AOUT binaries are not supported for this architecture.
53 architecture. This value is set in asm/param.h (see the HZ macro defined
|
| /linux-4.1.27/arch/mips/jazz/ |
| D | Kconfig | 9 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
21 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
32 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
| /linux-4.1.27/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 | vdso | 27 that it is correct for their architecture.)
|
| D | sysfs-firmware-efi-vars | 58 architecture.
|
| /linux-4.1.27/Documentation/usb/ |
| D | linux.inf | 19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
|
| /linux-4.1.27/Documentation/arm64/ |
| D | legacy_instructions.txt | 3 the architecture. The infrastructure code uses undefined instruction
14 have been obsoleted in the architecture, e.g., SWP
32 architecture. Deprecated instructions should default to emulation
|
| D | tagged-pointers.txt | 33 The architecture prevents the use of a tagged PC, so the upper byte will
|
| D | memory.txt | 7 Linux kernel. The architecture allows up to 4 levels of translation
|
| /linux-4.1.27/Documentation/nios2/ |
| D | README | 1 Linux on the Nios II architecture
16 Nios II is a 32-bit embedded-processor architecture designed specifically for the
|
| /linux-4.1.27/Documentation/arm/Samsung/ |
| D | GPIO.txt | 7 This outlines the Samsung GPIO implementation and the architecture
32 Pin configuration is specific to the Samsung architecture, with each SoC
|
| D | Overview.txt | 23 deals with the architecture and drivers specific to these devices.
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | headers_install.txt | 29 ARCH indicates which architecture to produce headers for, and defaults to the
30 current architecture. The linux/asm directory of the exported kernel headers
41 who create an architecture-independent tarball from the resulting include
|
| D | kbuild.txt | 83 deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
86 architecture.
90 Set ARCH to the architecture to be built.
91 In most cases the name of the architecture is the same as the
127 The implementation of "make install" is architecture specific
|
| D | makefiles.txt | 34 --- 6.1 Set variables to tweak the build to the architecture
76 architecture-specific information to the top Makefile.
102 *Arch developers* are people who work on an entire architecture, such
370 Another example are the architecture-specific Makefiles which
571 This functionality is useful for architecture Makefiles that try
779 but in the architecture makefiles where the kbuild infrastructure
814 for said architecture.
830 6) Finally, the architecture-specific part does any required post processing
836 --- 6.1 Set variables to tweak the build to the architecture
886 Append or modify as required per architecture.
[all …]
|
| /linux-4.1.27/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-4.1.27/Documentation/timers/ |
| D | highres.txt | 46 code out of the architecture-specific areas into a generic management
47 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
73 for various event driven functionalities is hardwired into the architecture
77 architecture. Another implication of the current design is that it is necessary
78 to touch all the architecture-specific implementations in order to provide new
84 to minimize the clock event related architecture dependent code to the pure
90 Clock event devices are registered either by the architecture dependent boot
112 architecture specific timer interrupt handlers and hands the control over the
127 The conversion of an architecture has no functional impact, but allows to
131 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
|
| D | timekeeping.txt | 9 If you grep through the kernel source you will find a number of architecture-
11 architecture-specific overrides of the sched_clock() function and some
112 number of nanoseconds since the system was started. An architecture may or
132 If an architecture does not provide its own implementation of this function,
134 jiffy frequency for the architecture. This will affect scheduling accuracy
147 architecture, special helper functions have been created to provide a
|
| /linux-4.1.27/tools/testing/selftests/x86/ |
| D | trivial_32bit_program.c | 8 # error wrong architecture
|
| D | trivial_64bit_program.c | 8 # error wrong architecture
|
| /linux-4.1.27/include/asm-generic/ |
| D | spinlock.h | 8 #error need an architecture specific asm/spinlock.h
|
| D | pgalloc.h | 7 #error need to implement an architecture specific asm/pgalloc.h
|
| D | tlbflush.h | 9 #error need to implement an architecture specific asm/tlbflush.h
|
| /linux-4.1.27/drivers/gpu/drm/amd/amdkfd/ |
| D | Kconfig | 2 # Heterogenous system architecture configuration
|
| /linux-4.1.27/arch/arm/mach-mmp/ |
| D | Kconfig | 49 ARMv7 architecture.
60 ARMv7 architecture.
71 ARMv7 architecture.
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 79 For more details about the x86 machine check architecture
80 see the Intel and AMD architecture manuals from their developer websites.
82 For more details about the architecture see
|
| D | kernel-stacks | 101 For more details see the Intel IA32 or AMD AMD64 architecture manuals.
|
| /linux-4.1.27/Documentation/vm/ |
| D | split_page_table_lock | 34 tables and the architecture supports it (see below).
49 Support of split page table lock by an architecture
56 Make sure the architecture doesn't use slab allocator for page table
|
| D | numa | 36 lives interesting. Rather, this architecture is a means to provide scalable
142 If the architecture supports--does not hide--memoryless nodes, then CPUs
|
| D | highmem.txt | 32 refer to as 'highmem'. There are various architecture dependent constraints on
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | switch.txt | 18 frameless architecture. In this architecture, the storage group
32 This architecture simplifies the management and configuration of both
42 device onto different targets. However in this architecture the LUN is
|
| /linux-4.1.27/arch/ |
| D | Kconfig | 2 # General architecture dependent options
111 This symbol should be selected by an architecture if 64 bit
113 though it is not a 64 bit architecture.
127 This symbol should be selected by an architecture if it can
142 inline assembler that the architecture code provides in the
147 store-and-swap instructions if the architecture has them. It
152 Any architecture with load-and-swap or store-and-swap
270 bit-mapping of each registers and a unique architecture id.
497 An architecture supports choosing randomized locations for
|
| /linux-4.1.27/arch/tile/include/uapi/arch/ |
| D | abi.h | 40 # error Unrecognized architecture with __need_int_reg_t
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.mISDN | 2 the old I4L driver architecture for passiv ISDN cards.
|
| /linux-4.1.27/arch/powerpc/include/uapi/asm/ |
| D | bootx.h | 80 __u32 architecture; member
|
| /linux-4.1.27/arch/openrisc/ |
| D | README.openrisc | 5 target architecture, specifically, is the 32-bit OpenRISC 1000 family (or1k).
77 initial port of linux to OpenRISC/or32 architecture.
|
| D | TODO.openrisc | 12 which was an older name for the architecture. The name we've settled on is
|
| D | Kconfig | 68 Generic OpenRISC 1200 architecture
115 OpenRISC architecture makes it optional to have it implemented
|
| /linux-4.1.27/Documentation/prctl/ |
| D | seccomp_filter.txt | 46 prctl(2) call as the strict seccomp. If the architecture has
105 sensible. (The architecture dependency is because replacing
156 number without checking the architecture value. Why? On any
157 architecture that supports multiple system call invocation conventions,
171 Adding architecture support
175 architecture supports both ptrace_event and seccomp, it will be able to
|
| /linux-4.1.27/tools/usb/usbip/ |
| D | INSTALL | 92 same time, by placing the object files for each architecture in their
99 architecture at a time in the source code directory. After you have
100 installed the package for one architecture, use `make distclean' before
101 reconfiguring for another architecture.
112 architecture-specific files and architecture-independent files. If you
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | 00-INDEX | 4 - CPU Scheduler implementation hints for architecture specific code.
|
| D | sched-arch.txt | 1 CPU Scheduler implementation hints for architecture specific code
|
| D | sched-domains.txt | 69 Alternatively, the architecture may completely override the generic domain
|
| /linux-4.1.27/drivers/cpuidle/ |
| D | Kconfig.mips | 15 Processing System (CPS) architecture. In order to make use of
|
| D | Kconfig.arm | 12 provided by architecture code.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ufs.txt | 45 UFS has a layered communication architecture which is based on SCSI
48 UFS communication architecture consists of following layers,
83 UIC is the lowest layer of UFS layered architecture. It handles
|
| D | 53c700.txt | 24 endian architecture (used for the 700 on parisc).
126 endian architecture.
|
| D | ChangeLog.arcmsr | 52 ** change the architecture of arcmsr command queue list
|
| D | FlashPoint.txt | 113 FlashPoint architecture at all, that debate has not yet been settled either
|
| /linux-4.1.27/arch/frv/boot/ |
| D | Makefile | 57 @test "$(INITRD_VIRT)" != "" || (echo This architecture does not support INITRD; exit -1)
|
| /linux-4.1.27/arch/x86/um/ |
| D | setjmp_64.S | 4 # setjmp/longjmp for the x86-64 architecture
|
| D | setjmp_32.S | 4 # setjmp/longjmp for the i386 architecture
|
| /linux-4.1.27/Documentation/devicetree/bindings/timer/ |
| D | ti,keystone-timer.txt | 4 architecture devices. The timer can be configured as a general-purpose 64-bit
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-iommu-intel-iommu | 31 The architecture version as reported from the
|
| D | sysfs-devices-system-cpu | 50 architecture specific.
54 is architecture specific.
88 The actual value is architecture and platform dependent.
98 is architecture and platform dependent.
|
| D | pstore | 24 "mce" - architecture dependent data from fatal h/w error
|
| D | sysfs-platform-kim | 8 The device name flows down to architecture specific board
|
| D | sysfs-class-mic.txt | 9 Integrated Core (MIC) architecture that runs a Linux OS.
|
| /linux-4.1.27/arch/c6x/lib/ |
| D | memcpy_64plus.S | 1 ; Port on Texas Instruments TMS320C6x architecture
|
| D | csum_64plus.S | 4 ; Port on Texas Instruments TMS320C6x architecture
|
| /linux-4.1.27/arch/s390/ |
| D | Kconfig.debug | 27 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/arm/ |
| D | swp_emulation | 4 ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommeds
|
| D | README | 81 memory management, architecture definitions etc). For all future
155 Historically, CONFIG_ARCH_ was used for the bonafide architecture,
156 e.g. SA1100, as well as implementations of the architecture,
|
| D | tcm.txt | 10 Harvard-architecture, so there is an ITCM (instruction TCM)
61 There is an interface for using TCM on the ARM architecture
|
| D | memory.txt | 14 As the ARM architecture matures, it becomes necessary to reserve
|
| D | Porting | 119 by the architecture specific code later in the code (via the
|
| D | Interrupts | 5 major architecture-specific subsystems.
|
| /linux-4.1.27/Documentation/cpuidle/ |
| D | driver.txt | 11 architecture/platform dependent part of CPU idle states. Driver
|
| /linux-4.1.27/Documentation/cris/ |
| D | README | 1 Linux on the CRIS architecture
20 architecture in Axis Communication AB's range of embedded network CPU's,
54 ETRAX 100LX is CRISv10 architecture.
|
| /linux-4.1.27/Documentation/s390/ |
| D | kvm.txt | 24 In addition, on s390 the following architecture specific ioctls are supported:
58 In addition, on s390 the following architecture specific ioctls for the kvm-vm
84 In addition, on s390 the following architecture specific ioctls for the
|
| D | cds.txt | 24 The document does not intend to explain the ESA/390 hardware architecture in
85 Note: All explanations apply also to the 64 bit architecture s390x.
100 can be found in the architecture specific C header file
105 Different to other hardware platforms, the ESA/390 architecture doesn't define
108 the ESA/390 architecture has implemented a so called channel subsystem, that
115 where the ESA/390 architecture allows for 64k devices be attached.
117 Linux, however, was first built on the Intel PC architecture, with its two
149 or more CCWs) as input sets up the required architecture specific control blocks
|
| D | DASD | 22 support of the FBA and CKD architectures. For the FBA architecture
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace-design.txt | 8 Here we will cover the architecture pieces that the common function tracing
12 Note that this focuses on architecture implementation details only. If you
42 *highly* architecture/toolchain specific. We cannot help you in this regard,
47 how glibc has implemented the mcount function for your architecture. It might
118 consistent across the architecture ports -- easier to compare & contrast
165 more information). The only architecture-specific piece in it is the setup of
|
| /linux-4.1.27/arch/unicore32/mm/ |
| D | Kconfig | 3 # Select CPU types depending on the architecture selected. This selects
|
| /linux-4.1.27/arch/arc/plat-tb10x/ |
| D | Kconfig | 29 Abilis Systems. TB10x is based on the ARC700 CPU architecture.
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | core.txt | 30 architecture drivers (those pieces of code that do actual
35 speed limits (like LCD drivers on ARM architecture). Additionally, the
|
| D | user-guide.txt | 54 The following processors for the x86 architecture are supported by cpufreq:
80 The following processors for the sparc64 architecture are supported by
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-bench.txt | 149 Available routines are depend on the architecture.
181 Available routines are depend on the architecture.
|
| D | perf-record.txt | 247 each sample. List of captured registers depends on the architecture. This option
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | cpus.txt | 29 The ARM architecture, in accordance with the ePAPR, requires the cpus and cpu
44 Definition depends on ARM architecture version and
76 Usage and definition depend on ARM architecture version and
183 Usage and definition depend on ARM architecture version.
|
| D | coresight.txt | 3 CoreSight components are compliant with the ARM CoreSight architecture
|
| /linux-4.1.27/arch/c6x/kernel/ |
| D | vectors.S | 2 ; Port on Texas Instruments TMS320C6x architecture
|
| D | head.S | 2 ; Port on Texas Instruments TMS320C6x architecture
|
| D | entry.S | 2 ; Port on Texas Instruments TMS320C6x architecture
|
| /linux-4.1.27/arch/arm/mach-ux500/ |
| D | Kconfig | 20 Support for ST-Ericsson's Ux500 architecture
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | platform.txt | 183 The architecture code registers platform device data using the function
190 The architecture code calls parse_early_param() to parse the kernel
201 The architecture code may optionally force registration of all early
216 The architecture code calls early_platform_driver_probe() to match
|
| /linux-4.1.27/scripts/gdb/linux/ |
| D | utils.py | 116 return arch in gdb.newest_frame().architecture().name()
|
| /linux-4.1.27/Documentation/networking/ |
| D | packet_mmap.txt | 259 the PACKET_MMAP buffer could hold only 32768 frames in a 32 bit architecture or
260 16384 in a 64 bit architecture. For information on these kernel versions
277 In a i386 architecture PAGE_SIZE is 4096 bytes
282 respectively, with an i386 architecture.
314 In a 2.4/2.6 kernel and the i386 architecture, the limit is 131072 bytes. The
318 In a 32 bit architecture, pointers are 4 bytes long, so the total number of
329 <pointer size>: depends on the architecture -- sizeof(void *)
330 <page size> : depends on the architecture -- PAGE_SIZE or getpagesize (2)
348 i386 architecture:
363 Actually, this buffer size is not possible with an i386 architecture.
|
| D | fore200e.txt | 45 on the endianness of the host architecture. The driver is shipped with
|
| D | nfc.txt | 7 This document covers the architecture overview, the device driver interface
|
| D | filter.txt | 53 architecture for user-level packet capture. In Proceedings of the
179 The BPF architecture consists of the following basic elements:
568 closer to the underlying architecture to mimic native instruction sets, so
668 that are used for argument passing on given architecture, the JIT compiler
1293 the underlying architecture.
|
| /linux-4.1.27/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 107 echo Do the torture scripts know about your architecture?
|
| /linux-4.1.27/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 59 The architecture is inspired by the design patterns "Protocol Layer" and
65 - Layered architecture (a la Streams), each layer in the CAIF
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/samsung/ |
| D | interrupt-combiner.txt | 3 Samsung's Exynos4 architecture includes a interrupt combiner controller which
|
| /linux-4.1.27/drivers/firmware/efi/ |
| D | Kconfig | 53 Select this config option from the architecture Kconfig if
|
| /linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 21 version of the architecture implemented.
|
| D | samsung,sysmmu.txt | 3 Samsung's Exynos architecture contains System MMUs that enables scattered
|
| /linux-4.1.27/kernel/irq/ |
| D | Kconfig | 2 # Options selectable by the architecture code
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/spear/ |
| D | shirq.txt | 3 SPEAr3xx architecture includes shared/multiplexed irqs for certain set
|
| /linux-4.1.27/lib/ |
| D | atomic64_test.c | 134 #warning Please implement atomic64_dec_if_positive for your architecture and select the above Kconf… in test_atomic64()
|
| D | Kconfig.debug | 315 # Select this config option from the architecture Kconfig, if it
317 # option on the architecture (regardless of KERNEL_DEBUG):
595 and other information provided by the architecture. Verbose
650 and exception stacks (if your architecture uses them). This
1575 developers working on architecture code.
|
| /linux-4.1.27/drivers/parport/ |
| D | Kconfig | 11 Select this config option from the architecture Kconfig if
12 the architecture might have PC parallel port hardware.
|
| /linux-4.1.27/kernel/power/ |
| D | Kconfig | 197 reboot. The architecture needs to support this, x86 for
200 The architecture specific code must provide the extern
204 The way the information is presented is architecture-
|
| /linux-4.1.27/Documentation/mic/ |
| D | mic_overview.txt | 2 card based on the Intel Many Integrated Core (MIC) architecture
|
| /linux-4.1.27/arch/arm/mm/ |
| D | Kconfig | 3 # Select CPU types depending on the architecture selected. This selects
241 The ARM1022E is an implementation of the ARMv5TE architecture
259 The ARM1026EJ-S is an implementation of the ARMv5TEJ architecture
417 # Figure out what processor architecture version we should be using.
564 Faraday ARM FA526 architecture, unified TLB with writeback cache
677 ARMv6 architecture deprecates use of the SWP/SWPB instructions.
1017 This option specifies the architecture can support big endian
|
| /linux-4.1.27/arch/hexagon/ |
| D | Kconfig | 32 Qualcomm Hexagon is a processor architecture designed for high
|
| /linux-4.1.27/arch/powerpc/platforms/44x/ |
| D | Kconfig | 246 that use a 440 based processor in the Virtex 5 FXT FPGA architecture.
375 # Xilinx Virtex 5 FXT FPGA architecture, selected by a Xilinx board above
|
| /linux-4.1.27/Documentation/virtual/kvm/devices/ |
| D | vm.txt | 9 The groups and attributes per virtual machine, if any, are architecture
|
| /linux-4.1.27/arch/mips/ |
| D | Kconfig | 1336 MIPS32 architecture. Most modern embedded systems with a 32-bit
1340 Release 2 of the MIPS32 architecture is available since several
1355 MIPS32 architecture. Most modern embedded systems with a 32-bit
1372 MIPS32 architecture. New MIPS processors, starting with the Warrior
1386 MIPS64 architecture. Many modern embedded systems with a 64-bit
1390 Release 2 of the MIPS64 architecture is available since several
1406 MIPS64 architecture. Many modern embedded systems with a 64-bit
1423 MIPS64 architecture. New MIPS processors, starting with the Warrior
1631 MIPS32 architecture including features from the 3.5 release such as
1651 MIPS32 architecture including features from release 5 such as
[all …]
|
| /linux-4.1.27/lib/raid6/ |
| D | int.uc | 53 * specially optimized using architecture-specific hacks.
|
| /linux-4.1.27/drivers/gpio/ |
| D | Kconfig | 8 Selecting this config option from the architecture Kconfig allows
9 the architecture to provide a custom asm/gpio.h implementation
16 Select this config option from the architecture Kconfig, if
17 it is possible to use gpiolib on the architecture, but let the
19 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
30 Selecting this from the architecture code will cause the gpiolib
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | integratorcp.dts | 17 * The Integrator/CP overall clocking architecture can be found in
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig.debug | 16 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/arm/SA1100/ |
| D | GraphicsClient | 21 r1 = 29 (this is the GraphicsClient architecture number)
|
| /linux-4.1.27/Documentation/power/ |
| D | interface.txt | 5 userspace, regardless of what architecture or platform one is
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | overview.txt | 59 on any architecture and machine.
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | Overview.txt | 10 by the 's3c2410' architecture of ARM Linux. Currently the S3C2410,
131 The architecture has been designed to support as many machines as can
|
| /linux-4.1.27/drivers/iommu/ |
| D | Kconfig | 349 Support for implementations of the ARM System MMU architecture
353 the ARM SMMU architecture.
|
| /linux-4.1.27/drivers/input/serio/ |
| D | Kconfig | 22 Select this config option from the architecture Kconfig if
23 the architecture might use a PC serio device (i8042) to
|
| /linux-4.1.27/mm/ |
| D | Kconfig | 96 # be done on your architecture, select this option. However,
108 # must select this option. This is usually for architecture platforms with
321 An architecture should select this if it implements the
604 architecture (ex, ARM) performs VM mapping faster than copying,
|
| /linux-4.1.27/drivers/video/console/ |
| D | Kconfig | 113 automatically select the primary display device (if the architecture
|
| /linux-4.1.27/Documentation/security/ |
| D | IMA-templates.txt | 41 It is during this phase that the advantages of the new architecture are
|
| /linux-4.1.27/Documentation/RCU/ |
| D | NMI-RCU.txt | 97 Important note: for this to work, the architecture in question must
|
| D | arrayRCU.txt | 50 which includes any memory barriers required on whatever architecture
|
| /linux-4.1.27/Documentation/tpm/ |
| D | xen-tpmfront.txt | 30 The architecture of vTPM is described below:
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | TODO | 41 in a control register. Not so with the ARM FPA11 architecture. To change
|
| /linux-4.1.27/Documentation/phy/ |
| D | samsung-usb2.txt | 8 The architecture of the USB 2.0 PHY module in Samsung SoCs is similar
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | README.pvrusb2 | 50 world.) The architecture allows for different APIs to
174 however the underlying architecture here was intended to allow for
|
| /linux-4.1.27/drivers/mtd/devices/ |
| D | lart.c | 47 #error This is for LART architecture only
|
| /linux-4.1.27/Documentation/parisc/ |
| D | registers | 82 The PA-RISC architecture defines 7 registers as "shadow registers".
|
| /linux-4.1.27/Documentation/x86/ |
| D | entry_64.txt | 7 The x86 architecture has quite a few different ways to jump into
|
| /linux-4.1.27/scripts/kconfig/ |
| D | Makefile | 110 $(if $(call configfiles),, $(error No configuration exists for this target on this architecture))
|
| /linux-4.1.27/drivers/staging/i2o/ |
| D | Kconfig | 5 The Intelligent Input/Output (I2O) architecture allows hardware
|
| /linux-4.1.27/arch/s390/kernel/ |
| D | head.S | 63 # subroutine to set architecture mode
|
| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 18 * Flexible object architecture optimized for network processing.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 1540 data format and layout are the same as documented in the architecture manual.
1557 and layout are the same as documented in the architecture manual.
1834 to a variable with the respective size. There can be architecture agnostic
1835 and architecture specific registers. Each have their own range of operation
2605 to know about. The id field is an architecture specific identifier for a
2667 The top 16 bits of the control field are architecture specific control
2680 we need to ensure the guest vCPUs architecture specific registers are
2683 The second part of the structure is architecture specific and
2688 structure containing architecture specific debug information.
2816 architecture. The ioctl takes parameters via the kvm_s390_skeys struct.
[all …]
|
| /linux-4.1.27/arch/powerpc/kvm/ |
| D | Kconfig | 193 Specification) interrupt controller architecture used on
|
| /linux-4.1.27/drivers/video/fbdev/ |
| D | 68328fb.c | 49 #error wrong architecture for the MC68x328 frame buffer device
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | submitting-patches | 26 architecture. If run-time testing was not achieved, it should be written
|
| /linux-4.1.27/arch/xtensa/ |
| D | Kconfig | 28 architecture supports all processor configurations and extensions,
136 The Xtensa architecture currently does not handle unaligned
|
| /linux-4.1.27/Documentation/dvb/ |
| D | ci.txt | 67 architecture can be implemented with this style, the definitions
|
| /linux-4.1.27/arch/m68k/q40/ |
| D | README | 103 Linux has some requirements wrt interrupt architecture, these are
|
| /linux-4.1.27/arch/powerpc/platforms/powermac/ |
| D | bootx_init.c | 520 if (bi->architecture != BOOT_ARCH_PCI) { in bootx_init()
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | of_unittest.txt | 10 architecture.
|
| D | usage-model.txt | 175 compatible list, and probably should be avoided for new architecture
201 During early boot, the architecture setup code calls of_scan_flat_dt()
|
| /linux-4.1.27/Documentation/locking/ |
| D | mutex-design.txt | 42 possible path. This logic is architecture specific. On x86-64, the
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | keystone-netcp.txt | 16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 37 achitecture||architecture
106 architechture||architecture
|
| /linux-4.1.27/tools/perf/ |
| D | design.txt | 450 If your architecture does not have hardware performance metrics, you can
458 If your architecture does have hardware capabilities, you can override the
|
| /linux-4.1.27/fs/cramfs/ |
| D | README | 107 kernels, not even necessarily kernels of the same architecture if
|
| /linux-4.1.27/arch/arm/boot/compressed/ |
| D | head.S | 148 mov r7, r1 @ save architecture ID
546 mov r1, r7 @ restore architecture number
979 @ These match on the architecture ID
|
| /linux-4.1.27/arch/arm/kernel/ |
| D | head.S | 487 and r3, r9, #0x000f0000 @ architecture version
|
| /linux-4.1.27/drivers/usb/usbip/ |
| D | usbip_protocol.txt | 4 The USB/IP protocol follows a server/client architecture. The server exports the
|
| /linux-4.1.27/Documentation/fb/ |
| D | uvesafb.txt | 63 only and is the default option on that architecture.
|
| /linux-4.1.27/Documentation/rapidio/ |
| D | rapidio.txt | 20 The Linux RapidIO subsystem is architecture independent and therefore defines
21 architecture-specific interfaces that provide support for common RapidIO
|
| /linux-4.1.27/Documentation/metag/ |
| D | kernel-ABI.txt | 5 This document describes the Linux ABIs for the metag architecture, and has the
|
| /linux-4.1.27/drivers/pcmcia/ |
| D | Kconfig | 56 CardBus is a bus mastering architecture for PC-cards, which allows
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 322 Based on the architecture and type of image (relocatable or not), one
362 It is planned to make this a no-op on that architecture, but for now
|
| /linux-4.1.27/ |
| D | README | 182 depending on the architecture.
189 platforms of your architecture.
|
| /linux-4.1.27/Documentation/ia64/ |
| D | aliasing.txt | 24 The Itanium architecture requires that we avoid accessing the same
|
| /linux-4.1.27/kernel/trace/ |
| D | Kconfig | 112 # Minimum requirements an architecture has to meet for us to
120 # irqflags tracing for your architecture.
|
| /linux-4.1.27/drivers/input/joystick/ |
| D | analog.c | 176 #warning Precise timer not defined for this architecture.
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | net.txt | 39 Currently supported on x86_64 architecture, bpf_jit provides a framework
|
| /linux-4.1.27/arch/powerpc/platforms/ |
| D | Kconfig.cputype | 68 "Book 3E" variant of the architecture
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig.debug | 75 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | qe_firmware.txt | 60 The QE architecture allows for only one microcode present in I-RAM for each
|
| /linux-4.1.27/block/partitions/ |
| D | Kconfig | 9 architecture than your Linux system.
|
| /linux-4.1.27/tools/perf/config/ |
| D | Makefile | 289 …msg := $(warning DWARF register mappings have not been defined for architecture $(ARCH), DWARF sup…
|