Searched +full:keep +full:- +full:a +full:- +full:live (Results 1 – 25 of 40) sorted by relevance
12
| /Documentation/devicetree/bindings/soc/intel/ |
| D | intel,hps-copy-engine.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/soc/intel/intel,hps-copy-engine.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Matthew Gerlach <matthew.gerlach@linux.intel.com>
15 a bootable image from host memory to HPS DDR. Additionally, there is a
17 well as a keep-a-live indication to the host.
21 const: intel,hps-copy-engine
23 '#dma-cells':
30 - compatible
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 8 Userfaults allow the implementation of on-demand paging from userland
12 For example userfaults allows a proper and more optimal implementation
18 Userspace creates a new userfaultfd, initializes it, and registers one or more
20 region(s) result in a message being delivered to the userfaultfd, notifying
26 1) ``read/POLLIN`` protocol to notify a userland thread of the faults
38 Vmas are not suitable for page- (or hugepage) granular fault tracking
43 passed using unix domain sockets to a manager process, so the same
44 manager process could handle the userfaults of a multitude of
48 is a corner case that would currently return ``-EBUSY``).
53 Creating a userfaultfd
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | maxlinear,gpy2xx.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Michael Walle <michael@walle.cc>
14 - $ref: ethernet-phy.yaml#
17 maxlinear,use-broken-interrupts:
19 Interrupts are broken on some GPY2xx PHYs in that they keep the
20 interrupt line asserted for a random amount of time even after the
24 can live with the consequences, this property can be used to enable
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ---------------------------------
7 generally a desirably quality of a filesystem. On a spinning disk,
9 that the head actuator and disk must perform to access a data block,
13 effect of concentrating writes on a single erase block, which can speed
17 The first tool that ext4 uses to combat fragmentation is the multi-block
18 allocator. When a file is first created, the block allocator
23 files) then the file data gets written out in a single multi-block
24 extent. A second related trick that ext4 uses is delayed allocation.
25 Under this scheme, when a file needs more blocks to absorb file writes,
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 2 The object-lifetime debugging infrastructure
10 debugobjects is a generic infrastructure to track the life time of
15 - Activation of uninitialized objects
17 - Initialization of active objects
19 - Usage of freed/destroyed objects
22 can be compiled in with a minimal runtime impact and enabled on demand
23 with a kernel command line option.
28 A kernel subsystem needs to provide a data structure which describes the
33 information can be retrieved from a live system instead of hard core
39 - debug_object_init
[all …]
|
| /Documentation/mm/ |
| D | highmem.rst | 5 By: Peter Zijlstra <a.p.zijlstra@chello.nl>
14 impossible for the kernel to keep all of the available physical memory mapped
18 The part of (physical) memory not covered by a permanent mapping is what we
30 +--------+ 0xffffffff
32 +--------+ 0xc0000000
36 +--------+ 0x00000000
39 time, but because we need virtual address space for other things - including
40 temporary maps to access the rest of the physical memory - the actual direct
54 * kmap_local_page(), kmap_local_folio() - These functions are used to create
57 them. The only differences between them consist in the first taking a pointer
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 15 There are many situations where users are reluctant to reboot a system. It may
18 users want to also have a stable and secure system. Livepatching gives users
20 functions without a system reboot.
30 - The kernel probes are the most generic. The code can be redirected by
31 putting a breakpoint instruction instead of any instruction.
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
44 a base. A Kprobe is registered as a ftrace handler when the function entry
46 a live patch is called with the help of a custom ftrace handler. But there are
[all …]
|
| /Documentation/accounting/ |
| D | taskstats.rst | 2 Per-task statistics interface
6 Taskstats is a netlink-based interface for sending per-task and
7 per-process statistics from the kernel to userspace.
11 - efficiently provide statistics during lifetime of a task and on its exit
12 - unified interface for multiple accounting subsystems
13 - extensibility for use by future accounting patches
16 -----------
19 Linux task defined by struct task_struct. per-pid stats are the same as
20 per-task stats.
25 leader - a process is deemed alive as long as it has any task belonging to it.
[all …]
|
| /Documentation/security/ |
| D | self-protection.rst | 2 Kernel Self-Protection
5 Kernel self-protection is the design and implementation of systems and
7 the kernel itself. This covers a wide range of issues, including removing
10 this document, but it should serve as a reasonable starting point and
13 In the worst-case scenario, we assume an unprivileged local attacker
17 cover the more limited cases as well. A higher bar, and one that should
18 still be kept in mind, is protecting the kernel against a _privileged_
19 local attacker, since the root user has access to a vastly increased
23 The goals for successful self-protection systems would be that they
24 are effective, on by default, require no opt-in by developers, have no
[all …]
|
| D | ipe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Integrity Policy Enforcement (IPE) - Kernel Documentation
10 :doc:`IPE admin guide </admin-guide/LSM/ipe>`.
13 ---------------------
16 of a locked-down system. This system would be born-secure, and have
20 policy. A mandatory access control system would be present, and
21 as a result, xattrs would have to be protected. This lead to a selection
27 2. DM-Verity
29 Both options were carefully considered, however the choice to use DM-Verity
40 there must be some form of selector to determine whether a read should
[all …]
|
| /Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 sb1000 is a module network device driver for the General Instrument (also known
9 which is used by a number of cable TV companies to provide cable modem access.
10 It's a one-way downstream-only cable modem, meaning that your upstream net link
14 a great deal of thanks for this wonderful piece of code!
19 Support for this device is now a part of the standard Linux kernel. The
23 1. The "cmconfig" program. This is a utility which supplements "ifconfig"
26 2. Several PPP scripts which live in /etc/ppp to make connecting via your
36 - http://web.archive.org/web/%2E/http://home.adelphia.net/~siglercm/sb1000.html
37 - http://web.archive.org/web/%2E/http://linuxpower.cx/~cable/
[all …]
|
| /Documentation/virt/kvm/ |
| D | ppc-pv.rst | 1 .. SPDX-License-Identifier: GPL-2.0
25 Linux is running on KVM, a node /hypervisor exists. That node contains a
28 Once you determined you're running under a PV capable KVM, you can now use
34 Inside the device tree's /hypervisor node there's a property called
35 'hypercall-instructions'. This property contains at most 4 opcodes that make
36 up the hypercall. To call a hypercall, just call these instructions.
43 r0 - volatile
53 r12 - volatile
73 To enable communication between the hypervisor and guest there is a new shared
80 applicable to the target. For now, we always map the page to -4096. This way we
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
41 Part 1 defines what fsck tools are and the motivations for writing a new one.
42 Parts 2 and 3 present a high level overview of how online fsck process works
54 1. What is a Filesystem Check?
57 A Unix filesystem has four main responsibilities:
59 - Provide a hierarchy of names through which application programs can associate
[all …]
|
| /Documentation/bpf/ |
| D | verifier.rst | 16 At the start of the program the register R1 contains a pointer to context
32 After kernel function call, R1-R5 are reset to unreadable and
33 R0 has a return type of the function.
35 Since R6-R9 are callee saved, their state is preserved across the call.
44 is a correct program. If there was R1 instead of R6, it would have
56 will be rejected, since R1 doesn't have a valid pointer type at the time of
59 At the start R1 type is PTR_TO_CTX (a pointer to generic ``struct bpf_context``)
60 A callback is used to customize verifier to restrict eBPF program access to only
67 intends to load a word from address R6 + 8 and store it into R0
72 stack bounds, which are [-MAX_BPF_STACK, 0). In this example offset is 8,
[all …]
|
| /Documentation/process/ |
| D | 2.Process.rst | 6 Linux kernel development in the early 1990's was a pretty loose affair,
7 with relatively small numbers of users and developers involved. With a
9 course of one year, the kernel has since had to evolve a number of
10 processes to keep development happening smoothly. A solid understanding of
14 ---------------
16 The kernel developers use a loosely time-based release process, with a new
29 Every 5.x release is a major kernel release with new features, internal
30 API changes, and more. A typical release can contain about 13,000
32 the leading edge of Linux kernel development; the kernel uses a
35 A relatively straightforward discipline is followed with regard to the
[all …]
|
| D | management-style.rst | 6 This is a short document describing the preferred (or made up, depending
8 mirror the :ref:`process/coding-style.rst <codingstyle>` document to some
14 to do with reality. It started as a lark, but that doesn't mean that it
20 budget of your group, you're almost certainly not a kernel manager.
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
27 making it painfully obvious to the questioner that we don't have a clue
35 ------------
37 Everybody thinks managers make decisions, and that decision-making is
42 The name of the game is to **avoid** having to make a decision. In
43 particular, if somebody tells you "choose (a) or (b), we really need you
[all …]
|
| /Documentation/filesystems/ |
| D | configfs.rst | 2 Configfs - Userspace-driven Kernel Object Configuration
16 configfs is a ram-based filesystem that provides the converse of
17 sysfs's functionality. Where sysfs is a filesystem-based view of
18 kernel objects, configfs is a filesystem-based manager of kernel
21 With sysfs, an object is created in kernel (for example, when a device
27 representation, and sysfs is merely a window on all this.
29 A configfs config_item is created via an explicit userspace operation:
38 system. One is not a replacement for the other.
43 configfs can be compiled as a module or into the kernel. You can access
46 mount -t configfs none /config
[all …]
|
| D | ramfs-rootfs-initramfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 --------------
14 Ramfs is a very simple filesystem that exports Linux's disk caching
15 mechanisms (the page cache and dentry cache) as a dynamically resizable
16 RAM-based filesystem.
24 memory. A similar mechanism (the dentry cache) greatly speeds up access to
34 you're mounting the disk cache as a filesystem. Because of this, ramfs is not
39 ------------------
41 The older "ram disk" mechanism created a synthetic block device out of
42 an area of RAM and used it as backing store for a filesystem. This block
[all …]
|
| D | f2fs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 WHAT IS Flash-Friendly File System (F2FS)?
7 NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
8 been equipped on a variety systems ranging from mobile to server systems. Since
10 disks, a file system, an upper layer to the storage device, should adapt to the
13 F2FS is a file system exploiting NAND flash memory-based storage devices, which
14 is based on Log-structured File System (LFS). The design has been focused on
18 Since a NAND flash memory-based storage device shows different characteristic
20 F2FS and its tools support various parameters not only for configuring on-disk
24 a consistency checking tool (fsck.f2fs), and a debugging tool (dump.f2fs).
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | mmu.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 for presenting a standard x86 mmu to the guest, while translating guest
13 - correctness:
17 a particular implementation such as tlb size)
18 - security:
21 - performance:
23 - scaling:
25 - hardware:
27 - integration:
31 - dirty tracking:
[all …]
|
| /Documentation/doc-guide/ |
| D | contributing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Documentation is an important part of any software-development project.
8 developers work more effectively. Without top-quality documentation, a lot
9 of time is wasted in reverse-engineering the code and making avoidable
13 it needs to be to support a project of this size and importance.
16 Kernel documentation improvements can be made by developers at a variety of
17 skill levels; they are a relatively easy way to learn the kernel process in
18 general and find a place in the community. The bulk of what follows is the
23 ---------------------------
26 documentation to where it should be. This list contains a number of
[all …]
|
| /Documentation/networking/ |
| D | ip-sysctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
21 Default value of TTL field (Time To Live) for outgoing (but not
25 ip_no_pmtu_disc - INTEGER
26 Disable Path MTU Discovery. If enabled in mode 1 and a
27 fragmentation-required ICMP is received, the PMTU to this
37 Mode 3 is a hardened pmtu discover mode. The kernel will only
[all …]
|
| /Documentation/admin-guide/ |
| D | reporting-issues.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
11 Are you facing a regression with vanilla kernels from the same stable or
23 expect to be told about problems, which most of the time will be by email with a
27 <https://kernel.org/>`_. If the issue is present there, send a report.
29 The issue was fixed there, but you would like to see it resolved in a still
35 **General remarks**: When installing and testing a kernel as outlined above,
36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make
37 sure it's built and running in a healthy environment and not already tainted
42 issue, like the kernel and the distro used. In case of a regression, CC the
44 to pin-point the culprit with a bisection; if you succeed, include its
[all …]
|
| /Documentation/arch/arm/omap/ |
| D | dss.rst | 7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
11 panel and controller drivers are in drivers/video/omap2/. DSS1 and DSS2 live
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
[all …]
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
15 To configure a DSA switch a couple of commands need to be executed. In this
19 Every switch port acts as a different configurable Ethernet port
25 Every switch port except one upstream port is part of a configurable
32 Through DSA every port of a switch is handled like a normal linux Ethernet
42 - when a DSA user interface is brought up, the conduit interface is
44 - when the conduit interface is brought down, all DSA user interfaces are
56 a user interface
[all …]
|
12