Home
last modified time | relevance | path

Searched full:kernel (Results 1 – 25 of 6675) sorted by relevance

12345678910>>...267

/Linux-v6.6/Documentation/core-api/
Dkernel-api.rst2 The Linux Kernel API
9 .. kernel-doc:: include/linux/list.h
24 .. kernel-doc:: lib/vsprintf.c
27 .. kernel-doc:: include/linux/kstrtox.h
30 .. kernel-doc:: lib/kstrtox.c
33 .. kernel-doc:: lib/string_helpers.c
39 .. kernel-doc:: include/linux/fortify-string.h
42 .. kernel-doc:: lib/string.c
45 .. kernel-doc:: include/linux/string.h
48 .. kernel-doc:: mm/util.c
[all …]
Dmm-api.rst8 .. kernel-doc:: arch/x86/include/asm/uaccess.h
11 .. kernel-doc:: arch/x86/lib/usercopy_32.c
14 .. kernel-doc:: mm/gup.c
22 .. kernel-doc:: include/linux/gfp_types.h
25 .. kernel-doc:: include/linux/gfp_types.h
28 .. kernel-doc:: include/linux/gfp_types.h
31 .. kernel-doc:: include/linux/gfp_types.h
37 .. kernel-doc:: include/linux/slab.h
40 .. kernel-doc:: mm/slab.c
43 .. kernel-doc:: mm/slab_common.c
[all …]
/Linux-v6.6/Documentation/admin-guide/kdump/
Dkdump.rst11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
14 the reboot and is accessible to the dump-capture kernel.
23 When the system kernel boots, it reserves a small section of memory for
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
30 regardless of where the kernel loads. For simpler handling, the whole
31 low 1M is reserved to avoid any later kernel or device driver writing
[all …]
/Linux-v6.6/Documentation/driver-api/
Dbasics.rst7 .. kernel-doc:: include/linux/module.h
13 .. kernel-doc:: include/linux/mod_devicetable.h
21 .. kernel-doc:: include/linux/sched.h
24 .. kernel-doc:: kernel/sched/core.c
27 .. kernel-doc:: kernel/sched/cpupri.c
30 .. kernel-doc:: kernel/sched/fair.c
33 .. kernel-doc:: include/linux/completion.h
39 .. kernel-doc:: include/linux/jiffies.h
42 .. kernel-doc:: kernel/time/time.c
45 .. kernel-doc:: kernel/time/timer.c
[all …]
Dinfrastructure.rst7 .. kernel-doc:: include/linux/device.h
11 .. kernel-doc:: include/linux/device/bus.h
14 .. kernel-doc:: include/linux/device/class.h
17 .. kernel-doc:: include/linux/device/driver.h
23 .. kernel-doc:: drivers/base/init.c
26 .. kernel-doc:: include/linux/device/driver.h
29 .. kernel-doc:: drivers/base/driver.c
32 .. kernel-doc:: drivers/base/core.c
35 .. kernel-doc:: drivers/base/syscore.c
38 .. kernel-doc:: include/linux/device/class.h
[all …]
/Linux-v6.6/arch/arm/
DKconfig.debug7 bool "Export kernel pagetable layout to userspace via debugfs"
13 Say Y here if you want to show the kernel pagetable layout in a
14 debugfs file. This information is only useful for kernel developers
15 who are working in architecture specific areas of the kernel.
17 kernel.
27 This is useful for discovering cases where the kernel is leaving
38 Note that even if the check fails, your kernel is possibly
41 of other unfixed kernel bugs easier.
44 once the kernel has booted up - it's a one time check.
49 prompt "Choose kernel unwinder"
[all …]
/Linux-v6.6/scripts/
Dhead-object-list.txt14 arch/alpha/kernel/head.o
15 arch/arc/kernel/head.o
16 arch/arm/kernel/head-nommu.o
17 arch/arm/kernel/head.o
18 arch/csky/kernel/head.o
19 arch/hexagon/kernel/head.o
20 arch/ia64/kernel/head.o
21 arch/loongarch/kernel/head.o
24 arch/m68k/kernel/head.o
25 arch/m68k/kernel/sun3-head.o
[all …]
/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-kernel-mm-damon1 what: /sys/kernel/mm/damon/
3 Contact: SeongJae Park <sj@kernel.org>
8 What: /sys/kernel/mm/damon/admin/
10 Contact: SeongJae Park <sj@kernel.org>
14 What: /sys/kernel/mm/damon/admin/kdamonds/nr_kdamonds
16 Contact: SeongJae Park <sj@kernel.org>
21 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/state
23 Contact: SeongJae Park <sj@kernel.org>
37 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/pid
39 Contact: SeongJae Park <sj@kernel.org>
[all …]
Ddebugfs-driver-habanalabs1 What: /sys/kernel/debug/habanalabs/hl<n>/addr
4 Contact: ogabbay@kernel.org
11 What: /sys/kernel/debug/habanalabs/hl<n>/clk_gate
14 Contact: ogabbay@kernel.org
17 What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
20 Contact: ogabbay@kernel.org
24 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
27 Contact: ogabbay@kernel.org
31 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
34 Contact: ogabbay@kernel.org
[all …]
Ddebugfs-hisi-hpre1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
9 Contact: linux-crypto@vger.kernel.org
14 What: /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
16 Contact: linux-crypto@vger.kernel.org
23 What: /sys/kernel/debug/hisi_hpre/<bdf>/current_qm
25 Contact: linux-crypto@vger.kernel.org
30 What: /sys/kernel/debug/hisi_hpre/<bdf>/alg_qos
32 Contact: linux-crypto@vger.kernel.org
[all …]
Ddebugfs-hisi-sec1 What: /sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
3 Contact: linux-crypto@vger.kernel.org
9 What: /sys/kernel/debug/hisi_sec2/<bdf>/current_qm
11 Contact: linux-crypto@vger.kernel.org
17 What: /sys/kernel/debug/hisi_sec2/<bdf>/alg_qos
19 Contact: linux-crypto@vger.kernel.org
27 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
29 Contact: linux-crypto@vger.kernel.org
34 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
36 Contact: linux-crypto@vger.kernel.org
[all …]
Ddebugfs-hisi-zip1 What: /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
9 Contact: linux-crypto@vger.kernel.org
13 What: /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
15 Contact: linux-crypto@vger.kernel.org
22 What: /sys/kernel/debug/hisi_zip/<bdf>/current_qm
24 Contact: linux-crypto@vger.kernel.org
29 What: /sys/kernel/debug/hisi_zip/<bdf>/alg_qos
31 Contact: linux-crypto@vger.kernel.org
[all …]
/Linux-v6.6/Documentation/networking/
Dkapi.rst11 .. kernel-doc:: include/linux/net.h
17 .. kernel-doc:: include/linux/skbuff.h
20 .. kernel-doc:: include/net/sock.h
23 .. kernel-doc:: net/socket.c
26 .. kernel-doc:: net/core/skbuff.c
29 .. kernel-doc:: net/core/sock.c
32 .. kernel-doc:: net/core/datagram.c
35 .. kernel-doc:: net/core/stream.c
41 .. kernel-doc:: net/core/filter.c
47 .. kernel-doc:: include/uapi/linux/gen_stats.h
[all …]
/Linux-v6.6/Documentation/gpu/
Ddrm-kms-helpers.rst7 userspace requests to kernel internal objects. Everything else is handled by a
39 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
42 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
53 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
59 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
65 .. kernel-doc:: include/drm/drm_atomic_helper.h
68 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
74 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
80 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
86 .. kernel-doc:: drivers/gpu/drm/drm_gem_atomic_helper.c
[all …]
Di915.rst19 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
22 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
25 .. kernel-doc:: drivers/gpu/drm/i915/intel_uncore.c
31 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
34 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
37 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
40 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
46 .. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
49 .. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
55 .. kernel-doc:: drivers/gpu/drm/i915/intel_gvt.c
[all …]
/Linux-v6.6/Documentation/sound/kernel-api/
Dalsa-driver-api.rst10 .. kernel-doc:: sound/core/init.c
14 .. kernel-doc:: sound/core/device.c
18 .. kernel-doc:: sound/core/sound.c
22 .. kernel-doc:: sound/core/memory.c
23 .. kernel-doc:: sound/core/memalloc.c
31 .. kernel-doc:: sound/core/pcm.c
32 .. kernel-doc:: sound/core/pcm_lib.c
33 .. kernel-doc:: sound/core/pcm_native.c
34 .. kernel-doc:: include/sound/pcm.h
38 .. kernel-doc:: sound/core/pcm_misc.c
[all …]
/Linux-v6.6/Documentation/filesystems/
Dapi-summary.rst14 .. kernel-doc:: include/linux/fs.h
20 .. kernel-doc:: fs/dcache.c
23 .. kernel-doc:: include/linux/dcache.h
29 .. kernel-doc:: fs/inode.c
32 .. kernel-doc:: fs/bad_inode.c
38 .. kernel-doc:: fs/super.c
44 .. kernel-doc:: fs/locks.c
47 .. kernel-doc:: fs/locks.c
53 .. kernel-doc:: fs/mpage.c
56 .. kernel-doc:: fs/namei.c
[all …]
/Linux-v6.6/Documentation/admin-guide/
DREADME.rst3 Linux kernel release 6.x <http://kernel.org/>
8 kernel, and what to do if something goes wrong.
39 Linux has also been ported to itself. You can now run the kernel as a
53 these typically contain kernel-specific installation notes for some
57 your kernel.
59 Installing the kernel source
62 - If you install the full sources, put the kernel tarball in a
68 Replace "X" with the version number of the latest kernel.
71 incomplete) set of kernel headers that are used by the library header
73 whatever the kernel-du-jour happens to be.
[all …]
Dtainted-kernels.rst4 The kernel will mark itself as 'tainted' when something occurs that might be
6 most of the time it's not a problem to run a tainted kernel; the information is
8 cause might be the event that got the kernel tainted. That's why bug reports
10 problems with an untainted kernel.
12 Note the kernel will remain tainted even after you undo what caused the taint
13 (i.e. unload a proprietary kernel module), to indicate the kernel remains not
14 trustworthy. That's also why the kernel will print the tainted state when it
15 notices an internal problem (a 'kernel bug'), a recoverable error
16 ('kernel oops') or a non-recoverable error ('kernel panic') and writes debug
25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened
[all …]
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dtracepoints.rst11 kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst).
13 For the list of support mlx5 events, check /sys/kernel/tracing/events/mlx5/.
19 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/tracing/set_event
20 $ cat /sys/kernel/tracing/trace
26 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/tracing/set_event
27 $ cat /sys/kernel/tracing/trace
33 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/tracing/set_event
34 $ cat /sys/kernel/tracing/trace
40 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/tracing/set_event
41 $ cat /sys/kernel/tracing/trace
[all …]
/Linux-v6.6/
DMAINTAINERS71 M: Steffen Klassert <klassert@kernel.org>
72 L: netdev@vger.kernel.org
79 L: netdev@vger.kernel.org
85 L: linux-scsi@vger.kernel.org
92 L: linux-scsi@vger.kernel.org
98 L: linux-bluetooth@vger.kernel.org
99 L: linux-wpan@vger.kernel.org
107 L: linux-hams@vger.kernel.org
113 L: linux-wireless@vger.kernel.org
115 W: https://wireless.wiki.kernel.org/
[all …]
/Linux-v6.6/Documentation/translations/it_IT/process/
Dhowto.rst8 Come partecipare allo sviluppo del kernel Linux
13 del kernel Linux e spiega come lavorare con la comunità di
14 sviluppo kernel Linux. Il documento non tratterà alcun aspetto
15 tecnico relativo alla programmazione del kernel, ma vi aiuterà
24 Dunque, volete imparare come diventare sviluppatori del kernel Linux?
33 Il kernel è scritto prevalentemente nel linguaggio C con alcune parti
35 Per lo sviluppo kernel è richiesta una buona conoscenza del linguaggio C.
46 Il kernel è stato scritto usando GNU C e la toolchain GNU.
48 estensioni che non sono previste in questo standard. Il kernel è un
52 Qualche volta è difficile comprendere gli assunti che il kernel ha
[all …]
/Linux-v6.6/Documentation/powerpc/
Dfirmware-assisted-dump.rst22 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
23 - Once enabled through kernel boot parameter, FADump can be
24 started/stopped through /sys/kernel/fadump_registered interface (see
32 with a fresh copy of the kernel. In particular,
36 is immediately available to the running kernel. And therefore,
44 - The first kernel registers the sections of memory with the
47 kernel during early boot.
55 that is required for a kernel to boot successfully when
61 boot memory size is not sufficient for second kernel to
73 - The freshly booted kernel will notice that there is a new node
[all …]
/Linux-v6.6/Documentation/process/
Dhowto.rst3 HOWTO do Linux kernel development
7 instructions on how to become a Linux kernel developer and how to learn
8 to work with the Linux kernel development community. It tries to not
9 contain anything related to the technical aspects of kernel programming,
20 So, you want to learn how to become a Linux kernel developer? Or you
27 The kernel is written mostly in C, with some architecture-dependent
29 kernel development. Assembly (any architecture) is not required unless
38 The kernel is written using GNU C and the GNU toolchain. While it
40 not featured in the standard. The kernel is a freestanding C
44 difficult to understand the assumptions the kernel has on the toolchain
[all …]
Dstable-api-nonsense.rst3 The Linux Kernel Driver Interface
11 kernel interface, nor does it have a stable kernel interface**.
15 Please realize that this article describes the **in kernel** interfaces, not
16 the kernel to userspace interfaces.
18 The kernel to userspace interface is the one that application programs use,
21 kernel that still work just fine on the latest 2.6 kernel release.
28 You think you want a stable kernel interface, but you really do not, and
30 you get that only if your driver is in the main kernel tree. You also
31 get lots of other good benefits if your driver is in the main kernel
40 It's only the odd person who wants to write a kernel driver that needs
[all …]

12345678910>>...267