Home
last modified time | relevance | path

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

12345678910>>...137

/Documentation/core-api/
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/slub.c
43 .. kernel-doc:: mm/slab_common.c
[all …]
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 …]
/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 …]
Dinfiniband.rst13 .. 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 …]
/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 …]
/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 …]
/Documentation/gpu/imagination/
Duapi.rst6 .. 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 …]
/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 …]
/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 …]
/Documentation/ABI/testing/
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-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 …]
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 …]
Dsysfs-kernel-btf1 What: /sys/kernel/btf
4 Contact: bpf@vger.kernel.org
6 Contains BTF type information and related data for kernel and
7 kernel modules.
9 What: /sys/kernel/btf/vmlinux
12 Contact: bpf@vger.kernel.org
14 Read-only binary attribute exposing kernel's own BTF type
15 information with description of all internal kernel types. See
19 What: /sys/kernel/btf/<module-name>
22 Contact: bpf@vger.kernel.org
[all …]
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>
41 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/pid
43 Contact: SeongJae Park <sj@kernel.org>
[all …]
Dsysfs-kernel-livepatch1 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 …]
Ddebugfs-driver-habanalabs1 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 …]
/Documentation/driver-api/media/drivers/
Dfrontends.rst12 .. 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 …]
/Documentation/process/
Dcve.rst8 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 …]
D8.Conclusion.rst6 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 …]
/Documentation/driver-api/pci/
Dpci.rst4 .. kernel-doc:: drivers/pci/pci.c
7 .. kernel-doc:: drivers/pci/iomap.c
10 .. kernel-doc:: drivers/pci/devres.c
13 .. kernel-doc:: drivers/pci/pci-driver.c
16 .. kernel-doc:: drivers/pci/remove.c
19 .. kernel-doc:: drivers/pci/search.c
22 .. kernel-doc:: drivers/pci/msi/msi.c
25 .. kernel-doc:: drivers/pci/bus.c
28 .. kernel-doc:: drivers/pci/access.c
31 .. kernel-doc:: drivers/pci/irq.c
[all …]
/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 …]
/Documentation/translations/it_IT/process/
D8.Conclusion.rst11 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 …]
/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 …]
/Documentation/admin-guide/
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 …]

12345678910>>...137