Home
last modified time | relevance | path

Searched +full:in +full:- +full:kernel (Results 1 – 25 of 1084) sorted by relevance

12345678910>>...44

/linux/Documentation/filesystems/
H A Didmappings.rst1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
16 in userspace is::
20 ``u`` indicates the first element in the upper idmapset ``U`` and ``k``
21 indicates the first element in the lower idmapset ``K``. The ``r`` parameter
24 we're talking about an id in the upper or lower idmapset.
26 To see what this looks like in practice, let's take the following idmapping::
32 u22 -> k10000
33 u23 -> k10001
34 u24 -> k10002
[all …]
/linux/Documentation/process/debugging/
H A Dkgdb.rst2 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.
15 Kdb is simplistic shell-style interface which you can use on a system
18 stop in a certain location. Kdb is not a source level debugger, although
19 you can set breakpoints and execute some basic kernel run control. Kdb
20 is mainly aimed at doing some analysis to aid in development or
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
[all …]
/linux/Documentation/arch/arm/
H A Dbooting.rst9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
11 In order to boot ARM Linux, you require a boot loader, which is a small
12 program that runs before the main kernel. The boot loader is expected
13 to initialise various devices, and eventually call the Linux kernel,
14 passing information to the kernel.
22 4. Setup the kernel tagged list.
24 6. Call the kernel image.
28 ---------------------------
36 kernel will use for volatile data storage in the system. It performs
37 this in a machine dependent manner. (It may use internal algorithms
[all …]
/linux/Documentation/process/
H A Dhowto.rst3 HOWTO do Linux kernel development
6 This is the be-all, end-all document on this topic. It contains
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,
10 but will help point you in the right direction for that.
12 If anything in this document becomes out of date, please send in patches
18 ------------
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
[all …]
H A Dstable-api-nonsense.rst3 The Linux Kernel Driver Interface
8 Greg Kroah-Hartman <greg@kroah.com>
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.
27 -----------------
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
[all …]
H A D4.Coding.rst6 While there is much to be said for a solid and community-oriented design
7 process, the proof of any kernel development project is in the resulting
13 number of ways in which kernel developers can go wrong. Then the focus
14 will shift toward doing things right and the tools which can help in that
19 ---------
24 The kernel has long had a standard coding style, described in
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
26 that time, the policies described in that file were taken as being, at most,
27 advisory. As a result, there is a substantial amount of code in the kernel
29 leads to two independent hazards for kernel developers.
[all …]
H A Dapplying-patches.rst3 Applying Patches To The Linux Kernel
11 This document is obsolete. In most cases, rather than using ``patch``
14 A frequently asked question on the Linux Kernel Mailing List is how to apply
15 a patch to the kernel or, more specifically, what base kernel a patch for
19 In addition to explaining how to apply and revert patches, a brief
20 description of the different kernel trees (and examples of how to apply
33 should both be present in the patch file metadata or be possible to deduce
41 (or patch) file and makes the changes to the source tree described in it.
43 Patches for the Linux kernel are generated relative to the parent directory
44 holding the kernel source dir.
[all …]
H A Dcve.rst8 regards to the kernel project, and CVE numbers were very often assigned
9 in inappropriate ways and for inappropriate reasons. Because of this,
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
19 process<../process/security-bugs>`.
21 A list of all assigned CVEs for the Linux kernel can be found in the
22 archives of the linux-cve mailing list, as seen on
[all …]
H A D3.Early-stage.rst3 Early-stage planning
6 When contemplating a Linux kernel development project, it can be tempting
7 to jump right in and start coding. As with any significant project,
9 line of code is written. Some time spent in early planning and
14 ----------------------
16 Like any engineering project, a successful kernel enhancement starts with a
17 clear description of the problem to be solved. In some cases, this step is
19 example. In others, though, it is tempting to confuse the real problem
24 by excessive latency in the system. The solution they arrived at was a
25 kernel module intended to hook into the Linux Security Module (LSM)
[all …]
/linux/Documentation/arch/x86/
H A Dpti.rst1 .. SPDX-License-Identifier: GPL-2.0
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
25 comments in pti.c).
27 This approach helps to ensure that side-channel attacks leveraging
30 time. Once enabled at compile-time, it can be disabled at boot with
31 the 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
[all …]
H A Dboot.rst1 .. SPDX-License-Identifier: GPL-2.0
7 On the x86 platform, the Linux kernel uses a rather complicated boot
9 well as the desire in the early days to have the kernel itself be a
11 expectations in the PC industry caused by the effective demise of
12 real-mode DOS as a mainstream operating system.
20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as
22 boot loader and the kernel. setup.S made relocatable,
26 Protocol 2.01 (Kernel 1.3.76) Added a heap overrun warning.
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
[all …]
H A Dkernel-stacks.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Kernel Stacks
7 Kernel stacks on x86-64 bit
14 Like all other architectures, x86_64 has a kernel stack for every
17 zombie. While the thread is in user space the kernel stack is empty
20 In addition to the per thread stacks, there are specialized stacks
21 associated with each CPU. These stacks are only used while the kernel
22 is in control on that CPU; when a CPU returns to user space the
29 kernel switches from the current task to the interrupt stack. Like
31 for kernel interrupt processing without having to increase the size
[all …]
/linux/include/uapi/linux/
H A Ddm-log-userspace.h1 /* SPDX-License-Identifier: LGPL-2.0+ WITH Linux-syscall-note */
3 * Copyright (C) 2006-2009 Red Hat, Inc.
12 #include <linux/dm-ioctl.h> /* For DM_UUID_LEN */
15 * The device-mapper userspace log module consists of a kernel component and
16 * a user-space component. The kernel component implements the API defined
17 * in dm-dirty-log.h. Its purpose is simply to pass the parameters and
18 * return values of those API functions between kernel and user-space.
20 * Below are defined the 'request_types' - DM_ULOG_CTR, DM_ULOG_DTR, etc.
21 * These request types represent the different functions in the device-mapper
22 * dirty log API. Each of these is described in more detail below.
[all …]
/linux/Documentation/translations/it_IT/process/
H A D2.Process.rst1 .. include:: ../disclaimer-ita.rst
11 Lo sviluppo del Kernel agli inizi degli anno '90 era abbastanza libero, con
14 il kernel da allora ha messo in atto un certo numero di procedure per rendere
19 -------------------
21 Il kernel Linux utilizza un modello di sviluppo a rilascio continuo,
22 vagamente basato sul tempo. Un nuovo rilascio principale del kernel (che
30 .. [1] A rigor di termini, il kernel Linux non utilizza uno schema di
40 "finestra di inclusione" viene dichiarata aperta. In quel momento il codice
42 viene incluso nel ramo principale del kernel. La maggior parte delle
49 raccolti e, verificati in anticipo. Il funzionamento di tale procedimento
[all …]
H A D1.Intro.rst1 .. include:: ../disclaimer-ita.rst
12 ------------------
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:
18 disponibilità immediata agli utilizzatori, supporto della comunità in
20 del kernel.
21 Il codice che contribuisce al kernel Linux deve essere reso disponibile sotto
22 una licenza GPL-compatibile.
25 il ciclo di rilascio del kernel, ed i meccanismi della finestra
28 liste di discussione. Gli sviluppatori che sono in attesa di poter sviluppare
[all …]
H A Dadding-syscalls.rst1 .. include:: ../disclaimer-ita.rst
3 :Original: :ref:`Documentation/process/adding-syscalls.rst <addsyscalls>`
12 nuove chiamate di sistema al kernel Linux; questo è da considerarsi come
14 :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`.
18 ------------------------------------
22 siano il punto di interazione fra spazio utente e kernel più tradizionale ed
23 ovvio, esistono altre possibilità - scegliete quella che meglio si adatta alle
26 - Se le operazioni coinvolte possono rassomigliare a quelle di un filesystem,
29 funzionalità in un modulo kernel piuttosto che essere sviluppata nel cuore
30 del kernel.
[all …]
/linux/Documentation/security/
H A Dself-protection.rst2 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
9 and actively detecting attack attempts. Not all topics are explored in
13 In the worst-case scenario, we assume an unprivileged local attacker
14 has arbitrary read and write access to the kernel's memory. In many
16 but with systems in place that defend against the worst case we'll
18 still be kept in mind, is protecting the kernel against a _privileged_
21 kernel modules.)
[all …]
/linux/arch/loongarch/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
220 menu "Kernel type and options"
223 prompt "Kernel type"
227 bool "32-bit kernel"
229 Select this option if you want to build a 32-bit kernel.
232 bool "64-bit kernel"
234 Select this option if you want to build a 64-bit kernel.
241 prompt "32-bit kernel sub-type"
244 bool "32-bit kernel for LA32R"
246 Select this option if you want to build a 32-bit kernel for
[all …]
/linux/Documentation/bpf/
H A Dbpf_devel_QA.rst10 Documentation/process/submitting-patches.rst. This document only describes
20 Q: How do I report bugs for BPF kernel code?
21 --------------------------------------------
22 A: Since all BPF kernel development as well as bpftool and iproute2 BPF
23 loader development happens through the bpf kernel mailing list,
27 bpf@vger.kernel.org
32 maintainers to Cc (from kernel ``MAINTAINERS`` file):
34 * Alexei Starovoitov <ast@kernel.org>
37 In case a buggy commit has already been identified, make sure to keep
38 the actual commit authors in Cc as well for the report. They can
[all …]
/linux/arch/arm/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
50 # https://github.com/llvm/llvm-project/commit/d130f402642fba3d065aacb506cb061c899558de
168 The ARM series is a line of low-power-consumption RISC chip designs
170 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
171 manufactured, but legacy ARM-based PC hardware remains popular in
179 relocations. The combined range is -/+ 256 MiB, which is usually
272 Patch phys-to-virt and virt-to-phys translation functions at
274 kernel in system memory.
276 This can only be used with non-XIP MMU kernels where the base
280 this feature (eg, building a kernel for a single machine) and
[all …]
/linux/drivers/base/firmware_loader/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
9 This enables the firmware loading facility in the kernel. The kernel
10 will first look for built-in firmware, if it has any. Next, it will
11 look for the requested firmware in a series of filesystem paths:
13 o firmware_class path module parameter or kernel boot param
19 Enabling this feature only increases your kernel image by about
23 You typically want this built-in (=y) but you can also enable this
24 as a module, in which case the firmware_class module will be built.
25 You also want to be sure to enable this built-in if you are going to
26 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
[all …]
/linux/Documentation/admin-guide/
H A Dreporting-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
7 "*We don't cause regressions*" is the first rule of Linux kernel development;
11 This document describes what the rule means for users and how the Linux kernel's
13 for kernel developers are left to Documentation/process/handling-regressions.rst.
19 #. It's a regression if something running fine with one Linux kernel works worse
20 or not at all with a newer version. Note, the newer kernel has to be compiled
22 and other fine print in more detail.
24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
28 <https://lore.kernel.org/regressions/>`_ (regressions@lists.linux.dev).
31 Linux kernel regression tracking bot "regzbot" track the issue by specifying
[all …]
H A Dsysfs-rules.rst1 Rules on how to access information in sysfs
4 The kernel-exported sysfs exports internal kernel implementation details
5 and depends on internal kernel structures and layout. It is agreed upon
6 by the kernel developers that the Linux kernel does not provide a stable
8 may not be stable across kernel releases.
10 To minimize the risk of breaking users of sysfs, which are in most cases
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
[all …]
/linux/Documentation/dev-tools/
H A Dtesting-overview.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Kernel Testing Guide
8 There are a number of different tools for testing the Linux kernel, so knowing
16 The bulk of kernel tests are written using either the kselftest or KUnit
18 groups of tests easier, as well as providing helpers to aid in writing new
21 If you're looking to verify the behaviour of the Kernel — particularly specific
22 parts of the kernel — then you'll want to use KUnit or kselftest.
26 ------------------------------------------
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
29 for "white box" testing: because test code is part of the kernel, it can access
[all …]
/linux/Documentation/power/
H A Dfreezing-of-tasks.rst11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There is one per-task flag (PF_NOFREEZE) and three per-task states
19 The tasks that have PF_NOFREEZE unset (all user space tasks and some kernel
20 threads) are regarded as 'freezable' and treated in a special way before the
23 to system-wide suspend too).
26 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
27 static key freezer_active (as opposed to a per-task flag or state) is used to
31 wakes up all the kernel threads. All freezable tasks must react to that by
32 calling try_to_freeze(), which results in a call to __refrigerator() (defined
33 in kernel/freezer.c), which changes the task's state to TASK_FROZEN, and makes
[all …]

12345678910>>...44