Searched +full:in +full:- +full:kernel (Results 1 – 25 of 1039) sorted by relevance
12345678910>>...42
| /Documentation/filesystems/ |
| D | idmappings.rst | 1 .. 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 …]
|
| /Documentation/arch/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 …]
|
| /Documentation/arch/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 …]
|
| /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 | 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 …]
|
| D | cve.rst | 8 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 …]
|
| 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 | code-of-conduct-interpretation.rst | 3 Linux Kernel Contributor Covenant Code of Conduct Interpretation
8 open-source community is unique and the Linux kernel is no exception.
9 Because of this, this document describes how we in the Linux kernel
13 The Linux kernel development effort is a very personal process compared
15 ideas behind them will be carefully reviewed, often resulting in
17 improvements before the material can be included in the
18 kernel. Know that this happens because everyone involved wants to see
21 system kernel ever, and we do not want to do anything to cause the
25 -----------
27 The Code of Conduct uses the term "maintainers" numerous times. In the
[all …]
|
| D | 2.Process.rst | 6 Linux kernel development in the early 1990's was a pretty loose affair,
8 user base in the millions and with some 2,000 developers involved over the
9 course of one year, the kernel has since had to evolve a number of
11 how the process works is required in order to be an effective part of it.
14 ---------------
16 The kernel developers use a loosely time-based release process, with a new
17 major kernel release happening every two or three months. The recent
29 Every 5.x release is a major kernel release with new features, internal
32 the leading edge of Linux kernel development; the kernel uses a
39 community) is merged into the mainline kernel. The bulk of changes for a
[all …]
|
| D | 4.Coding.rst | 6 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 …]
|
| D | 3.Early-stage.rst | 3 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 …]
|
| /Documentation/arch/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 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 …]
|
| /Documentation/admin-guide/ |
| D | README.rst | 3 Linux kernel release 6.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 …]
|
| D | reporting-issues.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
13 <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list
14 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
17 mailing list (stable@vger.kernel.org) and CC the regressions list
19 list for the subsystem in question.
21 In all other cases try your best guess which kernel part might be causing the
24 mailing list in CC. Check the destination's archives for matching reports;
25 search the `LKML <https://lore.kernel.org/lkml/>`_ and the web, too. If you
26 don't find any to join, install `the latest mainline kernel
[all …]
|
| D | tainted-kernels.rst | 2 ---------------
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
[all …]
|
| /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 …]
|
| /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 …]
|
| D | 4.Coding.rst | 1 .. include:: ../disclaimer-ita.rst
13 del kernel si trova nel codice stesso. È il codice che sarà esaminato dagli
18 sulle diverse casistiche nelle quali gli sviluppatori kernel possono
20 correttamente" e sugli strumenti che possono essere utili in questa missione.
23 --------
28 Il kernel ha da tempo delle norme sullo stile di codifica che sono descritte in
29 :ref:`Documentation/translations/it_IT/process/coding-style.rst <codingstyle>`.
30 Per la maggior parte del tempo, la politica descritta in quel file è stata
32 codice nel kernel che non rispetta le linee guida relative allo stile.
34 sviluppatori kernel.
[all …]
|
| /Documentation/rust/ |
| D | testing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This document contains useful information how to test the Rust code in the
7 kernel.
11 - The KUnit tests.
12 - The ``#[test]`` tests.
13 - The Kselftests.
16 ---------------
18 These are the tests that come from the examples in the Rust documentation. They
27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
29 Alternatively, KUnit can run them as kernel built-in at boot. Refer to
[all …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Documentation related to Rust within the kernel. To start using Rust
7 in the kernel, please read the quick-start.rst guide.
11 -------------------
13 The Rust support was merged in v6.1 into mainline in order to help in
14 determining whether Rust as a language was suitable for the kernel, i.e. worth
17 Currently, the Rust support is primarily intended for kernel developers and
18 maintainers interested in the Rust support, so that they can start working on
22 If you are an end user, please note that there are currently no in-tree
24 support is still in development/experimental, especially for certain kernel
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 KUnit - Linux Kernel Unit Testing
22 AOSP only supports running tests loaded with modules. Built-in
23 test execution support has been disabled. In addition, in order
25 needs to be enabled and kernel command line argument
28 The remaining KUnit documentation has been left as-is.
30 This section details the kernel unit testing framework.
35 KUnit (Kernel unit testing framework) provides a common framework for
36 unit tests within the Linux kernel. Using KUnit, you can define groups
37 of test cases called test suites. The tests either run on kernel boot
[all …]
|
| /Documentation/arch/arm64/ |
| D | booting.rst | 10 is relevant to all public releases of the AArch64 Linux kernel.
13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
15 level and exists only in secure mode. Both are architecturally optional.
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
41 the RAM in the machine, or any other method the boot loader designer
[all …]
|
| /Documentation/ABI/ |
| D | README | 1 This directory attempts to document the ABI between the Linux kernel and
4 interfaces should be used by userspace programs in different ways.
7 different subdirectories in this location. Interfaces may change levels
25 errors or security problems are found in them. Userspace
30 these interfaces, so that the kernel developers can easily
35 This directory documents interfaces that are still remaining in
36 the kernel, but are marked to be removed at some later point in
42 been removed from the kernel.
44 Every file in these directories will contain the following information:
48 KernelVersion: Kernel version this feature first showed up in.
[all …]
|
| /Documentation/bpf/ |
| D | bpf_licensing.rst | 10 "BPF" was originally introduced as BSD Packet Filter in
11 http://www.tcpdump.org/papers/bpf-usenix93.pdf. The corresponding instruction
15 However an instruction set is a specification for machine-language interaction,
17 application of a BSD license may be misleading in a certain context, as the
22 In 2014, the classic BPF instruction set was significantly extended. We
29 Using the eBPF instruction set requires implementing code in both kernel space
32 In Linux Kernel
33 ---------------
35 The reference implementations of the eBPF interpreter and various just-in-time
40 In User Space
[all …]
|
| /Documentation/security/ |
| D | self-protection.rst | 2 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 …]
|
12345678910>>...42