Searched full:kernel (Results 1 – 25 of 9673) sorted by relevance
12345678910>>...387
/kernel/linux/linux-5.10/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/kernel.h 30 .. kernel-doc:: include/linux/kernel.h 33 .. kernel-doc:: lib/kstrtox.c 36 .. kernel-doc:: lib/string_helpers.c 42 .. kernel-doc:: lib/string.c 45 .. kernel-doc:: include/linux/string.h 48 .. kernel-doc:: mm/util.c [all …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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 | 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 …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/arch/arm/ |
D | Kconfig.debug | 7 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 …]
|
/kernel/liteos_a/testsuites/kernel/ |
D | test.mk | 30 TESTLIB_SUBDIRS += kernel 57 TESTLIB_SUBDIRS += kernel/sample/kernel_base/ipc 63 TESTLIB_SUBDIRS += kernel/sample/kernel_base/core 68 TESTLIB_SUBDIRS += kernel/sample/kernel_base/mp 73 TESTLIB_SUBDIRS += kernel/sample/kernel_base/mem 78 TESTLIB_SUBDIRS += kernel/sample/kernel_base/vm 83 TESTLIB_SUBDIRS += kernel/sample/kernel_base/misc 88 TESTLIB_SUBDIRS += kernel/sample/kernel_base/om 93 TESTLIB_SUBDIRS += kernel/sample/kernel_base/atomic 101 TESTLIB_SUBDIRS += kernel/sample/kernel_extend/cpp [all …]
|
/kernel/linux/patches/ |
D | README.md | 11 …kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patches and OpenHa… 13 …on about Linux LTS 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 15 …on about Linux LTS 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 17 …, you can merge the driver code based on the chip platform and build the kernel image. All patches… 22 kernel/linux 25 │ ├── kernel.mk # Kernel build file 26 │ └── ohos.build # Kernel build component file 39 │ ├── kernel.patch # linux-5.10 rk3568 SOC patches 48 │ ├── small_common_defconfig # Common defconfig of the small-system kernel 49 … └── standard_common_defconfig # Common defconfig of the standard-system kernel [all …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/linux-5.10/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 …]
|
/kernel/linux/build/ |
D | README.md | 12 …kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patches and OpenHa… 14 …on about Linux LTS 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 16 …on about Linux LTS 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 18 …, you can merge the driver code based on the chip platform and build the kernel image. All patches… 24 **hi3516dv300_small.patch**: supports boot of the kernel of the Arm architecture (such as the DTS) … 29 kernel/linux/patches 41 ├── kernel.patch # linux-5.10 rk3568 SOC patches 49 …Apply the HDF kernel patches matching your kernel version. For details, see the method in **kernel… 59 …th and naming rules for the patches of the chip component in **kernel.mk** in the **kernel/linux/b… 62 DEVICE_PATCH_DIR := $(OHOS_BUILD_HOME)/kernel/linux/patches/${KERNEL_VERSION}/$(DEVICE_NAME)_patch [all …]
|
/kernel/linux/config/ |
D | README.md | 12 …kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patches and OpenHa… 14 …on about Linux LTS 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 16 …on about Linux LTS 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linu… 35 kernel/linux/config 42 │ ├── small_common_defconfig # Common defconfig of the small-system kernel 43 … └── standard_common_defconfig # Common defconfig of the standard-system kernel 50 ├── small_common_defconfig # Common defconfig of the small-system kernel 51 … └── standard_common_defconfig # Common defconfig of the standard-system kernel 58 …Apply the HDF kernel patches matching your kernel version. For details, see the method in **kernel… 68 …th and naming rules for the patches of the chip component in **kernel.mk** in the **kernel/linux/b… [all …]
|
/kernel/linux/linux-5.10/ |
D | MAINTAINERS | 1 List of maintainers and how to submit kernel changes 15 them onto the kernel channel and await results. This is especially 24 module and built into the kernel. 36 generalized kernel feature ready for next time. 66 please Cc: security@kernel.org, especially if the maintainer 147 M: Steffen Klassert <klassert@kernel.org> 148 L: netdev@vger.kernel.org 155 L: netdev@vger.kernel.org 161 L: linux-scsi@vger.kernel.org 168 L: linux-scsi@vger.kernel.org [all …]
|
/kernel/linux/linux-5.10/Documentation/translations/it_IT/process/ |
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 …]
|
/kernel/linux/linux-5.10/Documentation/process/ |
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 …]
|
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 …]
|
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 …]
|
/kernel/linux/linux-5.10/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 …]
|
12345678910>>...387