| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-damon | 1 what: /sys/kernel/mm/damon/
3 Contact: SJ Park <sj@kernel.org>
8 What: /sys/kernel/mm/damon/admin/
10 Contact: SJ Park <sj@kernel.org>
14 What: /sys/kernel/mm/damon/admin/kdamonds/nr_kdamonds
16 Contact: SJ Park <sj@kernel.org>
21 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/state
23 Contact: SJ Park <sj@kernel.org>
41 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/pid
43 Contact: SJ Park <sj@kernel.org>
[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 …]
|
| H A D | sysfs-kernel-livepatch | 1 What: /sys/kernel/livepatch
4 Contact: live-patching@vger.kernel.org
6 Interface for kernel live patching
8 The /sys/kernel/livepatch directory contains subdirectories for
11 What: /sys/kernel/livepatch/<patch>
14 Contact: live-patching@vger.kernel.org
16 The patch directory contains subdirectories for each kernel
19 What: /sys/kernel/livepatch/<patch>/enabled
22 Contact: live-patching@vger.kernel.org
28 What: /sys/kernel/livepatch/<patch>/transition
[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/ |
| H A D | MAINTAINERS | 73 L: netdev@vger.kernel.org
78 M: Steffen Klassert <klassert@kernel.org>
79 L: netdev@vger.kernel.org
86 L: netdev@vger.kernel.org
92 L: linux-scsi@vger.kernel.org
99 L: linux-scsi@vger.kernel.org
105 L: linux-bluetooth@vger.kernel.org
106 L: linux-wpan@vger.kernel.org
114 L: linux-wireless@vger.kernel.org
116 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> <abel.vesa@linaro.org>
16 Abel Vesa <abelvesa@kernel.org> <abelvesa@gmail.com>
45 Alexander Sverdlin <alex@sverdlin.org> <asv@kernel.org>
50 Alexei Starovoitov <ast@kernel.org> <alexei.starovoitov@gmail.com>
51 Alexei Starovoitov <ast@kernel.org> <ast@fb.com>
52 Alexei Starovoitov <ast@kernel.org> <ast@plumgrid.com>
55 Alex Elder <elder@kernel.org>
56 Alex Elder <elder@kernel.org> <aelder@sgi.com>
57 Alex Elder <elder@kernel.org> <alex.elder@linaro.org>
[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 | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
8 directory found in the kernel source distribution. Start with the
11 kernel APIs are documented using the kerneldoc mechanism; "make htmldocs"
16 Various web sites discuss kernel development at all levels of detail. Your
18 information on many specific kernel topics can be found via the LWN kernel
21 https://lwn.net/Kernel/Index/
23 Beyond that, a valuable resource for kernel developers is:
27 And, of course, one should not forget https://kernel.org/, the definitive
28 location for kernel release information.
30 There are a number of books on kernel development:
[all …]
|
| /linux/Documentation/translations/pt_BR/process/ |
| H A D | cve.rst | 10 relação ao projeto do kernel, e os números CVE foram frequentemente atribuídos
12 de desenvolvimento do kernel tendeu a evitá-los. No entanto, a combinação da
15 do kernel, deixou claro que a comunidade do kernel deve controlar
18 A equipe de desenvolvedores do kernel Linux tem a capacidade de atribuir CVEs
19 para possíveis problemas de segurança do kernel Linux. Essa atribuição é
20 independente do processo normal de relato de bugs de segurança do kernel
23 Uma lista de todos os CVEs atribuídos ao kernel Linux pode ser encontrada nos
25 https://lore.kernel.org/linux-cve-announce/. Para receber notificações sobre
27 <https://subspace.kernel.org/subscribing.html>`_ nessa lista de discussão.
32 Como parte do processo normal de lançamento estável, alterações do kernel que
[all …]
|
| H A D | 8.Conclusion.rst | 6 Há inúmeras fontes de informação sobre o desenvolvimento do kernel Linux e
8 encontrado na distribuição do código-fonte do kernel. Comece com o arquivo de
11 do kernel são documentadas usando o mecanismo kerneldoc; "make htmldocs" ou
16 Vários sites discutem o desenvolvimento do kernel em todos os níveis de
18 fonte; informações sobre muitos tópicos específicos do kernel podem ser
19 encontradas através do índice do kernel do LWN em:
21 https://lwn.net/Kernel/Index/
23 Além disso, um recurso valioso para os desenvolvedores do kernel é:
26 E, claro, não se deve esquecer o https://kernel.org/, o local definitivo
27 para informações sobre os lançamentos do kernel.
[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/process/debugging/ |
| H A D | kgdb.rst | 2 Using kgdb, kdb and the kernel debugger internals
10 The kernel has two different debugger front ends (kdb and kgdb) which
13 configure the kernel properly at compile and runtime.
19 you can set breakpoints and execute some basic kernel run control. Kdb
21 diagnosing kernel problems. You can access some symbols by name in
22 kernel built-ins or in kernel modules if the code was built with
26 kernel. It is used along with gdb to debug a Linux kernel. The
27 expectation is that gdb can be used to "break in" to the kernel to
30 application. It is possible to place breakpoints in kernel code and
34 development machine and the other is the target machine. The kernel to
[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 …]
|
| H A D | kernel-docs.rst | 3 :Original: :ref:`Documentation/process/kernel-docs.rst <kernel_docs>`
8 Índice de documentación adicional del kernel
12 correo de linux-kernel cuando las mismas preguntas, solicitando sugerencias
16 desarrolladores se interesan por el kernel. Sin embargo, leer las fuentes
27 de parches del kernel. Cualquier corrección, idea o comentario también es
41 Documentos en el árbol del kernel Linux
51 :Descripción: Documentación que viene con las fuentes del kernel,
59 * Título: **Linux Kernel Mailing List Glossary**
64 :Palabras Clave: glosario terminos, linux-kernel.
67 during discussion of the Linux kernel".
[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/driver-api/media/drivers/ |
| H A D | frontends.rst | 12 .. kernel-doc:: drivers/media/dvb-frontends/a8293.h
13 .. kernel-doc:: drivers/media/dvb-frontends/af9013.h
14 .. kernel-doc:: drivers/media/dvb-frontends/ascot2e.h
15 .. kernel-doc:: drivers/media/dvb-frontends/cxd2820r.h
16 .. kernel-doc:: drivers/media/dvb-frontends/drxk.h
17 .. kernel-doc:: drivers/media/dvb-frontends/dvb-pll.h
18 .. kernel-doc:: drivers/media/dvb-frontends/helene.h
19 .. kernel-doc:: drivers/media/dvb-frontends/horus3a.h
20 .. kernel-doc:: drivers/media/dvb-frontends/ix2505v.h
21 .. kernel-doc:: drivers/media/dvb-frontends/m88ds3103.h
[all …]
|
| /linux/Documentation/translations/it_IT/process/ |
| H A D | 8.Conclusion.rst | 11 Esistono numerose fonti di informazioni sullo sviluppo del kernel Linux
13 che si trova nei sorgenti kernel.
17 anch'esso qualcosa che tutti gli sviluppatori del kernel dovrebbero leggere.
18 Molte API interne al kernel sono documentate utilizzando il meccanismo
24 Diversi siti web approfondiscono lo sviluppo del kernel ad ogni livello
26 http://lwn.net/ come fonte; usando l'indice 'kernel' su LWN troverete
27 molti argomenti specifici sul kernel:
29 http://lwn.net/Kernel/Index/
31 Oltre a ciò, una risorsa valida per gli sviluppatori kernel è:
35 E, ovviamente, una fonte da non dimenticare è http://kernel.org/, il luogo
[all …]
|
| H A D | 1.Intro.rst | 14 Il resto di questa sezione riguarda il processo di sviluppo del kernel e
17 per il kernel debba essere incorporato nel kernel ufficiale, fra le quali:
20 del kernel.
21 Il codice che contribuisce al kernel Linux deve essere reso disponibile sotto
25 il ciclo di rilascio del kernel, ed i meccanismi della finestra
29 qualcosa per il kernel sono invitati ad individuare e sistemare bachi come
40 nell'assicurarvi che le modifiche per il kernel siano corrette.
63 del kernel.
68 Il kernel Linux, ha oltre 8 milioni di linee di codice e ben oltre 1000
71 questo kernel si è evoluto nel miglior componente per sistemi operativi
[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 …]
|
| /linux/Documentation/arch/x86/ |
| H A D | pti.rst | 11 countermeasure against attacks on the shared user/kernel address
16 the kernel is entered via syscalls, interrupts or exceptions, the
17 page tables are switched to the full "kernel" copy. When the system
20 The userspace page tables contain only a minimal amount of kernel
21 data: only what is needed to enter/exit the kernel such as the
31 the 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
36 When PTI is enabled, the kernel manages two sets of page tables.
39 that the kernel can use for things like copy_to_user().
41 Although _complete_, the user portion of the kernel page tables is
43 that any missed kernel->user CR3 switch will immediately crash
[all …]
|