| /linux/Documentation/core-api/ |
| H A D | kernel-api.rst | 2 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 …]
|
| H A D | mm-api.rst | 8 .. 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/slub.c
43 .. kernel-doc:: mm/slab_common.c
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | basics.rst | 7 .. 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 …]
|
| H A D | infiniband.rst | 13 .. kernel-doc:: drivers/infiniband/core/iwpm_util.h
16 .. kernel-doc:: drivers/infiniband/core/cq.c
19 .. kernel-doc:: drivers/infiniband/core/cm.c
22 .. kernel-doc:: drivers/infiniband/core/rw.c
25 .. kernel-doc:: drivers/infiniband/core/device.c
28 .. kernel-doc:: drivers/infiniband/core/verbs.c
31 .. kernel-doc:: drivers/infiniband/core/packer.c
34 .. kernel-doc:: drivers/infiniband/core/sa_query.c
37 .. kernel-doc:: drivers/infiniband/core/ud_header.c
40 .. kernel-doc:: drivers/infiniband/core/umem.c
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-damon | 1 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>
41 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/pid
43 Contact: SeongJae Park <sj@kernel
[all...] |
| H A D | debugfs-driver-habanalabs | 1 What: /sys/kernel/debug/accel/<parent_device>/addr
4 Contact: ogabbay@kernel.org
11 What: /sys/kernel/debug/accel/<parent_device>/clk_gate
14 Contact: ogabbay@kernel.org
17 What: /sys/kernel/debug/accel/<parent_device>/command_buffers
20 Contact: ogabbay@kernel.org
24 What: /sys/kernel/debug/accel/<parent_device>/command_submission
27 Contact: ogabbay@kernel.org
31 What: /sys/kernel/debug/accel/<parent_device>/command_submission_jobs
34 Contact: ogabbay@kernel.org
[all …]
|
| /linux/Documentation/gpu/ |
| H A D | drm-kms-helpers.rst | 7 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 …]
|
| /linux/ |
| H A D | MAINTAINERS | 71 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 …]
|
| H A D | .mailmap | 14 Abel Vesa <abelvesa@kernel.org> <abel.vesa@nxp.com>
15 Abel Vesa <abelvesa@kernel.org> <abelvesa@gmail.com>
37 Alexei Starovoitov <ast@kernel.org> <alexei.starovoitov@gmail.com>
38 Alexei Starovoitov <ast@kernel.org> <ast@fb.com>
39 Alexei Starovoitov <ast@kernel.org> <ast@plumgrid.com>
42 Alex Elder <elder@kernel.org>
43 Alex Elder <elder@kernel.org> <aelder@sgi.com>
44 Alex Elder <elder@kernel.org> <alex.elder@linaro.org>
45 Alex Elder <elder@kernel.org> <alex.elder@linary.org>
46 Alex Elder <elder@kernel.org> <elder@dreamhost.com>
[all …]
|
| /linux/scripts/ |
| H A D | head-object-list.txt | 14 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/loongarch/kernel/head.o
23 arch/m68k/kernel/head.o
24 arch/m68k/kernel/sun3-head.o
25 arch/microblaze/kernel/head.o
[all …]
|
| /linux/Documentation/gpu/imagination/ |
| H A D | uapi.rst | 6 .. kernel-doc:: include/uapi/drm/pvr_drm.h
11 .. kernel-doc:: include/uapi/drm/pvr_drm.h
14 .. kernel-doc:: include/uapi/drm/pvr_drm.h
19 .. kernel-doc:: include/uapi/drm/pvr_drm.h
22 .. kernel-doc:: include/uapi/drm/pvr_drm.h
27 .. kernel-doc:: include/uapi/drm/pvr_drm.h
30 .. kernel-doc:: include/uapi/drm/pvr_drm.h
33 .. kernel-doc:: include/uapi/drm/pvr_drm.h
36 .. kernel-doc:: include/uapi/drm/pvr_drm.h
43 .. kernel-doc:: include/uapi/drm/pvr_drm.h
[all …]
|
| /linux/Documentation/sound/kernel-api/ |
| H A D | alsa-driver-api.rst | 10 .. 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/Documentation/process/ |
| H A D | cve.rst | 8 regards to the kernel project, and CVE numbers were very often assigned
10 the kernel development community has tended to avoid them. However, the
13 outside of the kernel community has made it clear that the kernel
16 The Linux kernel developer team does have the ability to assign CVEs for
17 potential Linux kernel security issues. This assignment is independent
18 of the :doc:`normal Linux kernel security bug reporting
21 A list of all assigned CVEs for the Linux kernel can be found in the
23 https://lore.kernel.org/linux-cve-announce/. To get notice of the
25 <https://subspace.kernel.org/subscribing.html>`_ to that mailing list.
30 As part of the normal stable release process, kernel changes that are
[all …]
|
| H A D | howto.rst | 3 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 …]
|
| H A D | stable-api-nonsense.rst | 3 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 …]
|
| H A D | 1.Intro.rst | 9 The rest of this section covers the scope of the kernel development process
11 encounter there. There are a great many reasons why kernel code should be
12 merged into the official ("mainline") kernel, including automatic
14 influence the direction of kernel development. Code contributed to the
15 Linux kernel must be made available under a GPL-compatible license.
17 :ref:`development_process` introduces the development process, the kernel
21 with kernel development are encouraged to track down and fix bugs as an
30 which can help to ensure that kernel patches are correct.
48 for more information on kernel development.
53 The Linux kernel, at over 8 million lines of code and well over 1000
[all …]
|
| /linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | tracepoints.rst | 11 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/Documentation/admin-guide/ |
| H A D | README.rst | 3 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 …]
|
| H A D | tainted-kernels.rst | 4 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 …]
|
| H A D | reporting-issues.rst | 13 <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list
14 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
17 mailing list (stable@vger.kernel.org) and CC the regressions list
21 In all other cases try your best guess which kernel part might be causing the
25 search the `LKML <https://lore.kernel.org/lkml/>`_ and the web, too. If you
26 don't find any to join, install `the latest mainline kernel
27 <https://kernel.org/>`_. If the issue is present there, send a report.
35 **General remarks**: When installing and testing a kernel as outlined above,
40 If you are facing multiple issues with the Linux kernel at once, report each
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | firmware-assisted-dump.rst | 22 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/Documentation/translations/sp_SP/process/ |
| H A D | howto.rst | 8 Cómo participar en el desarrollo del kernel de Linux
12 sobre cómo convertirse en desarrollador del kernel de Linux y explica cómo
14 técnico relacionado con la programación del kernel, pero le ayudará
23 kernel de Linux? Tal vez su jefe le haya dicho, "Escriba un driver de
30 El kernel esta principalmente escrito en C, con algunas partes que son
32 es necesario para desarrollar en el kernel. Lenguaje ensamblador (en
42 El kernel está escrito usando GNU C y la cadena de herramientas GNU. Si
44 no aparecen en dicho estándar. El kernel usa un C independiente de entorno,
48 entender las suposiciones que el kernel hace respecto a la cadena de
64 El código fuente del kernel de Linux se publica bajo licencia GPL. Por
[all …]
|
| H A D | 1.Intro.rst | 15 kernel y los tipos de frustraciones que los desarrolladores y sus
17 código del kernel debe fusionarse con el kernel oficial (“mainline”),
20 desarrollo del kernel. El código contribuido al kernel de Linux debe
24 de lanzamiento del kernel y la mecánica de la "ventana de combinación"
28 comenzar con el desarrollo del kernel a encontrar y corregir errores como
38 las herramientas que pueden ayudar a garantizar que los parches del kernel
59 fuentes para obtener más información sobre el desarrollo del kernel.
64 El kernel de Linux, con más de 8 millones de líneas de código y más de
67 1991, este kernel ha evolucionado hasta convertirse en el mejor componente
82 kernel de Linux. Y los usuarios finales, también, a menudo desearán
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 80 third idmapping. The kernel will report unmapped ids as the overflowuid
125 In the context of the kernel an idmapping can be interpreted as mapping a range
126 of userspace ids into a range of kernel ids::
128 userspace-id:kernel-id:range
131 type ``uid_t`` or ``gid_t`` and a kernel id is always an element in the lower
134 types and "kernel id" will be used to refer to ``kuid_t`` and ``kgid_t``.
136 The kernel is mostly concerned with kernel ids. They are used when performing
139 kernel, or is passed by userspace to the kernel, or a raw device id that is
142 Note that we are only concerned with idmappings as the kernel stores them not
146 all kernel ids with ``k``. Ranges of idmappings will be prefixed with ``r``. So
[all …]
|
| /linux/Documentation/security/ |
| H A D | self-protection.rst | 2 Kernel Self-Protection
5 Kernel self-protection is the design and implementation of systems and
6 structures within the Linux kernel to protect against security flaws in
7 the kernel itself. This covers a wide range of issues, including removing
14 has arbitrary read and write access to the kernel's memory. In many
18 still be kept in mind, is protecting the kernel against a _privileged_
21 kernel modules.)
25 performance impact, do not impede kernel debugging, and have tests. It
35 areas of the kernel that can be used to redirect execution. This ranges
36 from limiting the exposed APIs available to userspace, making in-kernel
[all …]
|