Home
last modified time | relevance | path

Searched full:arch (Results 1 – 25 of 362) sorted by relevance

12345678910>>...15

/Documentation/features/scripts/
Dfeatures-refresh.sh5 for F_FILE in Documentation/features/*/*/arch-support.txt; do
22 # arch) which contains K.
29 # 1) no arch provides support for F,
45 for ARCH_DIR in arch/*/; do
60 echo " | arch |status|" >> $T_FILE
62 for ARCH_DIR in arch/*/; do
63 ARCH=$(echo $ARCH_DIR | sed -e 's/^arch//g' | sed -e 's/\///g')
67 # Arch support status values for (O, K) are updated according
70 # - ("", K) is 'supported by a given arch', if there is a
71 # Kconfig file for that arch which contains K;
[all …]
/Documentation/kbuild/
Dmakefiles.rst14 arch/$(SRCARCH)/Makefile the arch Makefile.
27 configuration. The top Makefile textually includes an arch Makefile
28 with the name arch/$(SRCARCH)/Makefile. The arch Makefile supplies
55 *Arch developers* are people who work on an entire architecture, such
56 as sparc or x86. Arch developers need to know about the arch Makefile
62 This document is aimed towards normal developers and arch developers.
211 #arch/x86/lib/Makefile
220 Use of lib-y is normally restricted to ``lib/`` and ``arch/*/lib``.
287 arch/$(SRCARCH)/kernel/vmlinux.lds
291 # arch/x86/kernel/Makefile
[all …]
/Documentation/arch/sh/
Dnew-machine.rst19 in arch/sh/kernel/ directly, with board-specific headers ending up in
27 |-- arch
49 `-- arch
63 |-- arch
97 board in arch/sh/boards/ and adding rules to hook your board in with the
99 it makes more sense to have a common top-level arch/sh/boards/ directory
103 After you have setup your new arch/sh/boards/ directory, remember that you
107 as the arch/sh/boards/ directory name, though if your board is again part of
113 arch/sh/boards and the include/asm-sh/ hierarchy. In order to better
120 * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
[all …]
Dindex.rst25 .. kernel-doc:: arch/sh/kernel/cpu/sh4/sq.c
34 .. kernel-doc:: arch/sh/boards/mach-dreamcast/rtc.c
40 .. kernel-doc:: arch/sh/boards/mach-x3proto/ilsel.c
/Documentation/features/
Dlist-arch.sh9 ARCH=${1:-$(uname -m | sed 's/x86_64/x86/' | sed 's/i386/x86/')}
11 $(dirname $0)/../../scripts/get_feat.pl list --arch $ARCH
Darch-support.txt3 arch-support.txt file in each feature directory shows the arch
/Documentation/arch/arm/sa1100/
Dcerf.rst30 make ARCH=arm CROSS_COMPILE=arm-linux- cerfcube_defconfig
31 make ARCH=arm CROSS_COMPILE=arm-linux- zImage
32 make ARCH=arm CROSS_COMPILE=arm-linux- modules
33 cp arch/arm/boot/zImage <TFTP directory>
/Documentation/arch/powerpc/
Dbootwrapper.rst12 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
21 The boot wrapper is built from the makefile in arch/powerpc/boot/Makefile and
22 it uses the wrapper script (arch/powerpc/boot/wrapper) to generate target
43 `arch/powerpc/boot/cuboot.*.c`. Selection of the correct
62 file named arch/powerpc/boot/<platform>.c; but this
95 arch/powerpc/boot/dts/ directory. The Makefile selects the correct device
98 arch/powerpc/boot/dts/walnut.dts to build treeImage.walnut.
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
108 arch/powerpc is designed to support multiplatform kernels, which means
120 script' (found in arch/powerpc/boot/wrapper) is called by the Makefile and
Dmpc52xx.rst11 # <edit Makefile to set ARCH=ppc & CROSS_COMPILE=... ( also EXTRAVERSION
23 # <edit Makefile to set ARCH=ppc & CROSS_COMPILE=... ( also EXTRAVERSION
26 # cp your_initrd.gz arch/ppc/boot/images/ramdisk.image.gz
Dbooting.rst13 doesn't follow them properly. In addition, since the advent of the arch/powerpc
15 platforms which move into arch/powerpc will be required to use these rules as
53 trampoline located in arch/powerpc/kernel/prom_init.c to
96 arch/powerpc/Kconfig, following the example of PPC_PSERIES,
101 "arch/powerpc/platforms/myplatform/myboard_setup.c" and add it
/Documentation/features/time/arch-tick-broadcast/
Darch-support.txt2 # Feature name: arch-tick-broadcast
4 # description: arch provides tick_broadcast()
7 | arch |status|
/Documentation/arch/x86/
Dentry_64.rst8 arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
15 arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
21 The IDT vector assignments are listed in arch/x86/include/asm/irq_vectors.h.
/Documentation/trace/
Dftrace-design.rst126 function, call the arch-specific function ftrace_graph_caller which in turn
127 calls the arch-specific function prepare_ftrace_return. Neither of these
136 temporarily to have it point to the arch-specific function return_to_handler.
207 An arch may pass in a unique value (frame pointer) to both the entering and
223 You need very few things to get the syscalls tracing in an arch.
225 - Support HAVE_ARCH_TRACEHOOK (see arch/Kconfig).
227 of syscalls supported by the arch.
231 - If the system call table on this arch is more complicated than a simple array
235 this arch, define ARCH_HAS_SYSCALL_MATCH_SYM_NAME in asm/ftrace.h and
238 - Tag this arch as HAVE_SYSCALL_TRACEPOINTS.
[all …]
/Documentation/virt/kvm/
Dlocking.rst53 - vcpu->mutex is taken outside kvm->arch.hyperv.hv_lock and kvm->arch.xen.xen_lock
55 - kvm->arch.mmu_lock is an rwlock; critical sections for
56 kvm->arch.tdp_mmu_pages_lock and kvm->arch.mmu_unsync_pages_lock must
57 also take kvm->arch.mmu_lock
237 :Arch: any
244 :Arch: any
254 :Arch: any
261 :Arch: x86
269 :Arch: any
276 :Arch: any
[all …]
/Documentation/driver-api/
Ds390-drivers.rst30 Documentation/arch/s390/driver-model.rst.
41 Documentation/arch/s390/vfio-ccw.rst.
67 .. kernel-doc:: arch/s390/include/asm/cio.h
81 .. kernel-doc:: arch/s390/include/asm/ccwdev.h
97 .. kernel-doc:: arch/s390/include/uapi/asm/cmb.h
115 .. kernel-doc:: arch/s390/include/asm/ccwgroup.h
/Documentation/scheduler/
Dsched-arch.rst10 By default, the switch_to arch function is called with the runqueue
62 arch/x86/kernel/process.c has examples of both polling and
66 Possible arch/ problems
69 Possible arch problems I found (and either tried to fix or didn't):
/Documentation/arch/arm/
Darm.rst16 To build ARM Linux natively, you shouldn't have to alter the ARCH = line
24 ARCH = <whatever>
28 ARCH = arm
43 (arch/arm/boot/Image). A compressed image can be built by doing a
71 `arch-*` machine/platform specific header files
88 To this end, we now have arch/arm/mach-$(MACHINE) directories which are
91 machines, there should be a corresponding arch/arm/mach-$(MACHINE)/include/mach
123 include it in with the C file, and not the arch/arm/lib directory. This
187 classes are given directories - arch/arm/mach-<class> - which contain
/Documentation/translations/zh_CN/arch/riscv/
Dpatch-acceptance.rst5 :Original: Documentation/arch/riscv/patch-acceptance.rst
13 arch/riscv 开发者维护指南
/Documentation/admin-guide/
Defi-stub.rst10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
32 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
37 arch/arm/boot/zImage should be copied to the system partition, and it
38 may not need to be renamed. Similarly for arm64, arch/arm64/boot/Image
/Documentation/arch/arm/pxa/
Dmfp.rst54 see arch/arm/mach-pxa/mfp-pxa300.h)
202 - arch/arm/mach-pxa/include/mach/mfp.h
208 - arch/arm/mach-pxa/mfp-pxa3xx.h
213 - arch/arm/mach-pxa/mfp-pxa2xx.h
217 - arch/arm/mach-pxa/mfp-pxa25x.h
218 arch/arm/mach-pxa/mfp-pxa27x.h
219 arch/arm/mach-pxa/mfp-pxa300.h
220 arch/arm/mach-pxa/mfp-pxa320.h
221 arch/arm/mach-pxa/mfp-pxa930.h
225 - arch/arm/mach-pxa/mfp-pxa3xx.c
[all …]
/Documentation/core-api/irq/
Dirqflags-tracing.rst27 - add and enable TRACE_IRQFLAGS_SUPPORT in their arch level Kconfig file
36 two do not match. Usually most of the time for arch support for
40 lockdep complaint in the irq-flags-tracing functions arch support is
/Documentation/features/core/eBPF-JIT/
Darch-support.txt4 # description: arch supports eBPF JIT optimizations
7 | arch |status|
/Documentation/features/perf/perf-regs/
Darch-support.txt4 # description: arch supports perf events register access
7 | arch |status|
/Documentation/features/time/context-tracking/
Darch-support.txt4 # description: arch supports user context tracking for NO_HZ_FULL
7 | arch |status|
/Documentation/features/debug/user-ret-profiler/
Darch-support.txt4 # description: arch supports user-space return from system call profiler
7 | arch |status|

12345678910>>...15