| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | maint-appx.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Kernel Maintenance
10 This section describes construction of the Yocto Project kernel source
12 Linux kernel repositories. These kernel repositories are found under the
13 heading "Yocto Linux Kernel" at :yocto_git:`/` and
16 for every BSP and feature in the product. Those feature descriptions
18 divisions found in a Yocto Linux kernel. Thus, the Yocto Project Linux
19 kernel repository (or tree) and accompanying Metadata in the
20 ``yocto-kernel-cache`` are built.
23 particular Yocto Project Linux kernel repository and use it to build
[all …]
|
| H A D | concepts-appx.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Advanced Kernel Concepts
7 Yocto Project Kernel Development and Maintenance
11 other kernels, are based off the Linux kernel releases from
12 https://www.kernel.org. At the beginning of a major Linux kernel
13 development cycle, the Yocto Project team chooses a Linux kernel based
15 final upstream ``kernel.org`` versions, and Yocto Project feature
16 requirements. Typically, the Linux kernel chosen is in the final stages
17 of development by the Linux community. In other words, the Linux kernel
18 is in the release candidate or "rc" phase and has yet to reach final
[all …]
|
| H A D | advanced.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Working with Advanced Metadata (``yocto-kernel-cache``)
10 In addition to supporting configuration fragments and patches, the Yocto
11 Project kernel tools also support rich
16 BSPs and Linux kernel types.
18 Kernel Metadata exists in many places. One area in the
19 :ref:`overview-manual/development-environment:yocto project source repositories`
20 is the ``yocto-kernel-cache`` Git repository. You can find this repository
21 grouped under the "Yocto Linux Kernel" heading in the
24 Kernel development tools ("kern-tools") are also available in the Yocto Project
[all …]
|
| H A D | common.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
8 with the Yocto Project Linux kernel. These tasks include preparing your
9 host development system for kernel development, preparing a layer,
10 modifying an existing recipe, patching the kernel, configuring the
11 kernel, iterative development, working with your own sources, and
12 incorporating out-of-tree modules.
16 The examples presented in this chapter work with the Yocto Project
19 Preparing the Build Host to Work on the Kernel
22 Before you can do any kernel development, you need to be sure your build
24 set up, see the ":doc:`/dev-manual/start`" section in
[all …]
|
| H A D | intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 are you will work with the Linux kernel. This manual describes how to
12 set up your build host to support kernel development, introduces the
13 kernel development process, provides background information on the Yocto
14 Linux kernel :term:`Metadata`, describes
15 common tasks you can perform using the kernel tools, shows you how to
16 use the kernel Metadata needed to work with the kernel inside the Yocto
18 and maintains Yocto Linux kernel Git repositories and Metadata.
20 Each Yocto Project release has a set of Yocto Linux kernel recipes,
21 whose Git repositories you can view in the Yocto
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/process/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/Documentation/admin-guide/kdump/ |
| H A 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. For simpler handling, the whole
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/packagegroups/ |
| H A D | packagegroup-base.bb | 11 packagegroup-base \
12 packagegroup-base-extended \
13 packagegroup-distro-base \
14 packagegroup-machine-base \
16 ${@bb.utils.contains("MACHINE_FEATURES", "acpi", "packagegroup-base-acpi", "",d)} \
17 ${@bb.utils.contains("MACHINE_FEATURES", "alsa", "packagegroup-base-alsa", "", d)} \
18 ${@bb.utils.contains("MACHINE_FEATURES", "ext2", "packagegroup-base-ext2", "", d)} \
19 ${@bb.utils.contains("MACHINE_FEATURES", "vfat", "packagegroup-base-vfat", "", d)} \
20 … ${@bb.utils.contains("MACHINE_FEATURES", "keyboard", "packagegroup-base-keyboard", "", d)} \
21 ${@bb.utils.contains("MACHINE_FEATURES", "pci", "packagegroup-base-pci", "",d)} \
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A 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 …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | dm-log-userspace.h | 1 /* 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 …]
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/security/ |
| H A 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 …]
|