Searched +full:in +full:- +full:kernel (Results 1 – 25 of 1103) sorted by relevance
12345678910>>...45
| /kernel/linux/linux-4.19/Documentation/dev-tools/ |
| 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.
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 …]
|
| /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.
11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 1.Intro.rst | 7 -----------------
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
13 availability to users, community support in many forms, and the ability to
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
18 release cycle, and the mechanics of the merge window. The various phases in
21 with kernel development are encouraged to track down and fix bugs as an
[all …]
|
| D | howto.rst | 3 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 …]
|
| D | stable-api-nonsense.rst | 3 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 …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | 1.Intro.rst | 5 -----------------
7 The rest of this section covers the scope of the kernel development process
9 encounter there. There are a great many reasons why kernel code should be
10 merged into the official ("mainline") kernel, including automatic
11 availability to users, community support in many forms, and the ability to
12 influence the direction of kernel development. Code contributed to the
13 Linux kernel must be made available under a GPL-compatible license.
15 :ref:`development_process` introduces the development process, the kernel
16 release cycle, and the mechanics of the merge window. The various phases in
19 with kernel development are encouraged to track down and fix bugs as an
[all …]
|
| D | howto.rst | 1 HOWTO do Linux kernel development
4 This is the be-all, end-all document on this topic. It contains
5 instructions on how to become a Linux kernel developer and how to learn
6 to work with the Linux kernel development community. It tries to not
7 contain anything related to the technical aspects of kernel programming,
8 but will help point you in the right direction for that.
10 If anything in this document becomes out of date, please send in patches
16 ------------
18 So, you want to learn how to become a Linux kernel developer? Or you
25 The kernel is written mostly in C, with some architecture-dependent
[all …]
|
| D | stable-api-nonsense.rst | 3 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 …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | README.rst | 3 Linux kernel release 4.x <http://kernel.org/>
8 kernel, and what to do if something goes wrong.
11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
[all …]
|
| /kernel/linux/linux-4.19/Documentation/arm/ |
| D | Booting | 7 The following documentation is relevant to 2.4.18-rmk6 and beyond.
9 In order to boot ARM Linux, you require a boot loader, which is a small
10 program that runs before the main kernel. The boot loader is expected
11 to initialise various devices, and eventually call the Linux kernel,
12 passing information to the kernel.
20 4. Setup the kernel tagged list.
22 6. Call the kernel image.
26 ---------------------------
32 kernel will use for volatile data storage in the system. It performs
33 this in a machine dependent manner. (It may use internal algorithms
[all …]
|
| /kernel/linux/linux-5.10/Documentation/translations/it_IT/process/ |
| D | howto.rst | 1 .. include:: ../disclaimer-ita.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à
18 Se qualsiasi cosa presente in questo documento diventasse obsoleta,
20 file, indicati in fondo al presente documento.
23 ------------
24 Dunque, volete imparare come diventare sviluppatori del kernel Linux?
30 di spiegare alcune delle ragioni per le quali la comunità lavora in un
[all …]
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| 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.
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 …]
|
| /kernel/linux/linux-4.19/Documentation/arm64/ |
| D | booting.txt | 8 is relevant to all public releases of the AArch64 Linux kernel.
11 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
12 counterpart. EL2 is the hypervisor level and exists only in non-secure
13 mode. EL3 is the highest priority level and exists only in secure mode.
17 is passed to the Linux kernel. This may include secure monitor and
26 3. Decompress the kernel image
27 4. Call the kernel image
31 ---------------------------
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 …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | booting.rst | 9 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 …]
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | boot.txt | 2 ---------------------------
4 On the x86 platform, the Linux kernel uses a rather complicated boot
6 well as the desire in the early days to have the kernel itself be a
8 expectations in the PC industry caused by the effective demise of
9 real-mode DOS as a mainstream operating system.
16 Protocol 2.00: (Kernel 1.3.73) Added bzImage and initrd support, as
18 boot loader and the kernel. setup.S made relocatable,
22 Protocol 2.01: (Kernel 1.3.76) Added a heap overrun warning.
24 Protocol 2.02: (Kernel 2.4.0-test3-pre3) New command line protocol.
27 safe for systems which use the EBDA from SMM or 32-bit
[all …]
|
| D | pti.txt | 5 countermeasure against attacks on the shared user/kernel address
10 the kernel is entered via syscalls, interrupts or exceptions, the
11 page tables are switched to the full "kernel" copy. When the system
14 The userspace page tables contain only a minimal amount of kernel
15 data: only what is needed to enter/exit the kernel such as the
19 comments in pti.c).
21 This approach helps to ensure that side-channel attacks leveraging
24 Once enabled at compile-time, it can be disabled at boot with the
25 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
30 When PTI is enabled, the kernel manages two sets of page tables.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
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
[all …]
|
| /kernel/linux/linux-4.19/Documentation/kdump/ |
| D | kdump.txt | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | booting.rst | 10 is relevant to all public releases of the AArch64 Linux kernel.
13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in non-secure
15 mode. EL3 is the highest priority level and exists only in secure mode.
19 is passed to the Linux kernel. This may include secure monitor and
28 3. Decompress the kernel image
29 4. Call the kernel image
33 ---------------------------
38 kernel will use for volatile data storage in the system. It performs
39 this in a machine dependent manner. (It may use internal algorithms
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | pti.rst | 1 .. 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 Once enabled at compile-time, it can be disabled at boot with the
31 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
[all …]
|
| /kernel/linux/patches/ |
| D | README.md | 1 # Patch<a name="EN-US_TOPIC_0000001078264110"></a>
3 - [Introduction](#section11660541593)
4 - [Directory Structure](#section21571344112)
5 - [Usage](#section1393789267)
6 - [Build](#section19369206113115)
7 - [Repositories Involved](#section27639463106)
11 …-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patc…
13 … 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
15 … 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
17 …, you can merge the driver code based on the chip platform and build the kernel image. All patches…
[all …]
|
| /kernel/linux/config/ |
| D | README.md | 1 # Config<a name="EN-US_TOPIC_0000001102487950"></a>
3 - [Introduction](#section11660541593)
4 - [Composition of Config](#section28381947133910)
5 - [Directory Structure](#section161941989596)
6 - [Usage](#section1393789267)
7 - [Build](#section19369206113115)
8 - [Repositories Involved](#section1371113476307)
12 …-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patc…
14 … 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
16 … 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
[all …]
|
| /kernel/linux/linux-4.19/Documentation/wimax/ |
| D | README.i2400m | 4 (C) 2008 Intel Corporation < linux-wimax@intel.com >
7 and a basic Linux kernel WiMAX stack.
11 * Linux installation with Linux kernel 2.6.22 or newer (if building
16 + Linux kernel development package for the target kernel; to
17 build against your currently running kernel, you need to have
18 the kernel development package corresponding to the running
19 image installed (usually if your kernel is named
20 linux-VERSION, the development package is called
21 linux-dev-VERSION or linux-headers-VERSION).
26 2.1. Compilation of the drivers included in the kernel
[all …]
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
6 During the development of the Linux/ppc64 kernel, and more specifically, the
8 was decided to enforce some strict rules regarding the kernel entry and
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
10 become the ppc32 kernel entry point and the way a new platform should be added
11 to the kernel. The legacy iSeries platform breaks those rules as it predates
12 this scheme, but no new board support will be accepted in the main tree that
13 doesn't follow them properly. In addition, since the advent of the arch/powerpc
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
[all …]
|
| /kernel/linux/build/ |
| D | README.md | 1 # Patch<a name="EN-US_TOPIC_0000001078264110"></a>
3 - [Introduction](#section11660541593)
4 - [Driver Patches for a Specific Chip Architecture (such as Hi3516D V300)](#section1521510717399)
5 - [Directory Structure](#section21571344112)
6 - [Usage](#section1393789267)
7 - [Build](#section19369206113115)
8 - [Repositories Involved](#section27639463106)
12 …-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has incorporated CVE patc…
14 … 4.19.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
16 … 5.10.y, visit the [official kernel website](https://git.kernel.org/pub/scm/linux/kernel/git/stabl…
[all …]
|
12345678910>>...45