Searched full:kernel (Results 1 – 25 of 2238) sorted by relevance
12345678910>>...90
| /Documentation/core-api/ |
| 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:: lib/string.c
42 .. kernel-doc:: include/linux/string.h
45 .. kernel-doc:: mm/util.c
49 Basic Kernel Library Functions
[all …]
|
| 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
28 .. kernel-doc:: include/linux/gfp.h
31 .. kernel-doc:: include/linux/gfp.h
34 .. kernel-doc:: include/linux/gfp.h
37 .. kernel-doc:: include/linux/gfp.h
43 .. kernel-doc:: include/linux/slab.h
46 .. kernel-doc:: mm/slab.c
49 .. kernel-doc:: mm/slab_common.c
[all …]
|
| /Documentation/driver-api/ |
| 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
36 .. kernel-doc:: kernel/time/timer.c
42 .. kernel-doc:: include/linux/wait.h
45 .. kernel-doc:: kernel/sched/wait.c
[all …]
|
| D | infrastructure.rst | 7 .. kernel-doc:: include/linux/device.h
14 .. kernel-doc:: drivers/base/init.c
17 .. kernel-doc:: drivers/base/driver.c
20 .. kernel-doc:: drivers/base/core.c
23 .. kernel-doc:: drivers/base/syscore.c
26 .. kernel-doc:: drivers/base/class.c
29 .. kernel-doc:: drivers/base/node.c
32 .. kernel-doc:: drivers/base/transport_class.c
35 .. kernel-doc:: drivers/base/dd.c
38 .. kernel-doc:: include/linux/platform_device.h
[all …]
|
| 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 …]
|
| /Documentation/networking/ |
| D | kapi.rst | 11 .. 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/admin-guide/kdump/ |
| D | kdump.rst | 11 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. Therefore, kexec backs up this
31 region just before rebooting into the dump-capture kernel.
[all …]
|
| /Documentation/filesystems/ |
| D | api-summary.rst | 14 .. 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/sound/kernel-api/ |
| 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 …]
|
| /Documentation/driver-api/media/drivers/ |
| 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 …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-hpre | 1 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>/regs
32 Contact: linux-crypto@vger.kernel.org
[all …]
|
| D | debugfs-hisi-sec | 1 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>/qm/qm_regs
19 Contact: linux-crypto@vger.kernel.org
24 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
26 Contact: linux-crypto@vger.kernel.org
31 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/clear_enable
33 Contact: linux-crypto@vger.kernel.org
[all …]
|
| D | debugfs-hisi-zip | 1 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>/qm/regs
31 Contact: linux-crypto@vger.kernel.org
[all …]
|
| 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 …]
|
| /Documentation/admin-guide/ |
| D | README.rst | 3 Linux kernel release 5.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 …]
|
| 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 …]
|
| /Documentation/process/ |
| D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
8 directory found in the kernel source distribution. The top-level :ref:`process/howto.rst <process_…
11 are also something which all kernel developers should
12 read. Many internal kernel APIs are documented using the kerneldoc
18 Various web sites discuss kernel development at all levels of detail. Your
20 information on many specific kernel topics can be found via the LWN kernel
23 https://lwn.net/Kernel/Index/
25 Beyond that, a valuable resource for kernel developers is:
29 And, of course, one should not forget https://kernel.org/, the definitive
30 location for kernel release information.
[all …]
|
| 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 …]
|
| /Documentation/translations/it_IT/process/ |
| D | 8.Conclusion.rst | 11 Esistono numerose fonti di informazioni sullo sviluppo del kernel Linux
13 che si trova nei sorgenti kernel.
18 anch'essi qualcosa che tutti gli sviluppatori del kernel dovrebbero leggere.
19 Molte API interne al kernel sono documentate utilizzando il meccanismo
25 Diversi siti web approfondiscono lo sviluppo del kernel ad ogni livello
27 http://lwn.net/ come fonte; usando l'indice 'kernel' su LWN troverete
28 molti argomenti specifici sul kernel:
30 http://lwn.net/Kernel/Index/
32 Oltre a ciò, una risorsa valida per gli sviluppatori kernel è:
36 E, ovviamente, una fonte da non dimenticare è http://kernel.org/, il luogo
[all …]
|
| D | howto.rst | 8 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 …]
|
| /Documentation/driver-api/pci/ |
| D | pci.rst | 4 .. kernel-doc:: drivers/pci/pci.c
7 .. kernel-doc:: drivers/pci/pci-driver.c
10 .. kernel-doc:: drivers/pci/remove.c
13 .. kernel-doc:: drivers/pci/search.c
16 .. kernel-doc:: drivers/pci/msi.c
19 .. kernel-doc:: drivers/pci/bus.c
22 .. kernel-doc:: drivers/pci/access.c
25 .. kernel-doc:: drivers/pci/irq.c
28 .. kernel-doc:: drivers/pci/probe.c
31 .. kernel-doc:: drivers/pci/slot.c
[all …]
|
| /Documentation/gpu/ |
| 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_simple_kms_helper.c
[all …]
|
| D | i915.rst | 19 .. 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 …]
|
| /Documentation/powerpc/ |
| 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 …]
|
| /Documentation/kbuild/ |
| D | headers_install.rst | 2 Exporting kernel headers for use by userspace
5 The "make headers_install" command exports the kernel's header files in a
8 The linux kernel's exported header files describe the API for user space
9 programs attempting to use kernel services. These kernel header files are
12 system calls. The C library's header files include the kernel header files
14 installed at the default location /usr/include and the kernel headers in
18 Kernel headers are backwards compatible, but not forwards compatible. This
19 means that a program built against a C library using older kernel headers
20 should run on a newer kernel (although it may not have access to new
21 features), but a program built against newer kernel headers may not work on an
[all …]
|
12345678910>>...90