Searched +full:existing +full:- +full:parts (Results 1 – 25 of 87) sorted by relevance
1234
| /Documentation/admin-guide/hw-vuln/ |
| D | vmscape.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 guest-userspace may be able to attack the guest-kernel using the hypervisor as
14 -------------------
19 - Skylake generation (Parts without Enhanced-IBRS)
20 - Cascade Lake generation - (Parts affected by ITS guest/host separation)
21 - Alder Lake and newer (Parts affected by BHI)
23 Note that, BHI affected parts that use BHB clearing software mitigation e.g.
27 - Zen series (families 0x17, 0x19, 0x1a)
30 - Family 0x18
33 ----------
[all …]
|
| D | reg-file-data-sampling.rst | 6 only affects Intel Atom parts(also branded as E-cores). RFDS may allow
9 ability to choose which data is inferred. CVE-2023-28746 is assigned to RFDS.
32 As an exception to this table, Intel Xeon E family parts ALDERLAKE(06_97H) and
37 affected and unaffected parts, but it is deemed not worth adding complexity as
38 the reporting is fixed automatically when these parts enumerate RFDS_NO.
51 -----------------
54 at C-state transitions.
57 ----------------------------------
58 Newer processors and microcode update on existing affected processors added new
62 - Bit 27 - RFDS_NO - When set, processor is not affected by RFDS.
[all …]
|
| /Documentation/devicetree/bindings/pwm/ |
| D | microchip,corepwm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Conor Dooley <conor.dooley@microchip.com>
16 https://www.microsemi.com/existing-parts/parts/152118
19 - $ref: pwm.yaml#
24 - const: microchip,corepwm-rtl-v4
32 "#pwm-cells":
37 microchip,sync-update-mask:
48 Each bit of "microchip,sync-update-mask" corresponds to a PWM channel & represents
[all …]
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 12 though they still must provide DMA-ready buffers (see
13 Documentation/core-api/dma-api-howto.rst). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
21 - URBs have an additional "transfer_dma" field, as well as a transfer_flags
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
29 - There's a new "generic DMA API", parts of which are usable by USB device
37 and effects like cache-trashing can impose subtle penalties.
[all …]
|
| D | hotplug.rst | 8 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
12 - Find a driver that can handle the device. That may involve
13 loading a kernel module; newer drivers can use module-init-tools
16 - Bind a driver to that device. Bus frameworks do that using a
19 - Tell other subsystems to configure the new device. Print
22 be driver-specific actions.
54 http://linux-hotplug.sourceforge.net
78 hotplugging is independent of ``usbdevfs``: you can do most essential parts
83 modules, and can invoke driver-specific setup scripts. The newest ones
84 leverage USB module-init-tools support. Later agents might unload drivers.
[all …]
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 10 ----------
14 --------
26 -----------
37 outside the confinement of all-or-nothing shared resources of legacy
45 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
53 -----------
59 even non-threaded applications if they have a need to disassociate
60 from default shared namespace. The following lists two use-cases
63 2.1 Per-security context namespaces
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 1. Porting tests to KUnit which are already known with an existing name.
17 example, non-deterministically producing false positives or negatives, or
25 is a set of test suites which test different parts of a kernel subsystem
29 ----------
59 ``linear-ranges``
62 ``qos-kunit-test``
63 This name should use underscores, and not have "kunit-test" as a
64 suffix. ``qos`` is also ambiguous as a subsystem name, because several parts
77 ------
[all …]
|
| D | architecture.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The KUnit architecture is divided into two parts:
9 - `In-Kernel Testing Framework`_
10 - `kunit_tool (Command-line Test Harness)`_
12 In-Kernel Testing Framework
19 - Organizes tests
20 - Reports test results
21 - Provides test utilities
24 ----------
32 ``generate_params`` is optional for non-parameterized tests.
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
50 - If the backing device can't or won't permit direct sharing,
[all …]
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at25.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christian Eggers <ceggers@arri.de>
15 - pattern: "^eeprom@[0-9a-f]{1,2}$"
16 - pattern: "^fram@[0-9a-f]{1,2}$"
20 # 'vendor' and 'model' parts of the first are the actual chip and the second
21 # item is fixed to "atmel,at25". Some existing bindings only have the
26 - items:
27 - enum:
[all …]
|
| /Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 54 * Remove in-order completion assumptions from DRM scheduler
75 * -1k to -1 Low priority
84 ----------------
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
87 * https://spec.oneapi.com/level-zero/latest/core/api.html#ze-command-queue-priority-t
91 The existing bonding uAPI is completely broken with GuC submission because
102 The new parallel submission uAPI consists of 3 parts:
110 ------------------------------
112 (e.g. split-frame on gen11+). The logical mapping of engine instances can change
114 logical mapping with the existing query engine info IOCTL. Also the GuC
[all …]
|
| D | i915_vm_bind.h | 1 /* SPDX-License-Identifier: MIT */
20 * any existing mappings.
32 * Flag to opt-in for VM_BIND mode of binding during VM creation.
51 * struct drm_i915_gem_timeline_fence - An input or output timeline fence.
74 #define __I915_TIMELINE_FENCE_UNKNOWN_FLAGS (-(I915_TIMELINE_FENCE_SIGNAL << 1))
86 * struct drm_i915_gem_vm_bind - VA to object mapping to bind.
98 * platform, for binding device local-memory objects, the @start, @offset and
102 * Error code -EINVAL will be returned if @start, @offset and @length are not
104 * -ENOSPC will be returned if the VA range specified can't be reserved.
107 * are not ordered. Furthermore, parts of the VM_BIND operation can be done
[all …]
|
| /Documentation/driver-api/ |
| D | reset.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
12 The reset controller API is split into two parts:
13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
25 --------
39 is self-clearing and can be used to trigger a predetermined pulse on the
64 reset inputs, which are mapped to an actual reset control on an existing reset
71 ---------------------------
[all …]
|
| D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
60 * Double-channel
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
67 * Chip-select row
70 accessed. Common chip-select rows for single channel are 64 bits, for
[all …]
|
| /Documentation/arch/riscv/ |
| D | vector.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Vector Extension Support for RISC-V Linux
8 order to support the use of the RISC-V Vector Extension.
11 ---------------------
19 are not portable to non-Linux, nor non-RISC-V environments, so it is discourage
27 argument consists of two 2-bit enablement statuses and a bit for inheritance
30 Enablement status is a tri-state value each occupying 2-bit of space in
33 * :c:macro:`PR_RISCV_V_VSTATE_CTRL_DEFAULT`: Use the system-wide default
34 enablement status on execve(). The system-wide default setting can be
43 arg: The control argument is a 5-bit value consisting of 3 parts, and
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
16 --------------------
26 -------
29 and functions to work with them. Objects are high-level abstractions
37 These objects are associated with corresponding parts of ELF object that
56 -------------------
63 ---
67 non-static libbpf symbols should have one of the prefixes mentioned in
72 -----------------
78 .. code-block:: c
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------
9 .. list-table::
11 :header-rows: 1
13 * - Group 0 Padding
14 - ext4 Super Block
15 - Group Descriptors
16 - Reserved GDT Blocks
17 - Data Block Bitmap
18 - inode Bitmap
[all …]
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 5 Last update: 2004-12-20 tlh
15 - gen_init_cpio, a program that builds a cpio-format archive
18 - initramfs, a chunk of code that unpacks the compressed cpio image
20 - klibc, a userspace C library, currently packaged separately, that is
23 The cpio file format used by initramfs is the "newc" (aka "cpio -H newc")
24 format, and is documented in the file "buffer-format.txt". There are
25 two ways to add an early userspace image: specify an existing cpio
30 -------------------
39 ---------------------
42 source parts rather than supplying a cpio archive. This method provides
[all …]
|
| /Documentation/target/ |
| D | tcmu-design.rst | 19 2) Writing a user pass-through handler
29 TCM is another name for LIO, an in-kernel iSCSI target (server).
30 Existing TCM targets run in the kernel. TCMU (TCM in Userspace)
34 The existing kernel provides modules for different SCSI transport
35 protocols. TCM also modularizes the data storage. There are existing
38 built-in modules are implemented entirely as kernel code.
41 ----------
52 use case that other non-kernel target solutions, such as tgt, are able
55 in these non-traditional networked storage systems, while still only
65 kernel, another approach is to create a userspace pass-through
[all …]
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| ST-Ericsson AB 2010
17 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
22 ST-Ericsson modems support a number of transports between modem
39 ! +------+ +------+
40 ! +------+! +------+!
42 +-------> !interf!+ ! API !+ <- CAIF Client APIs
43 ! +------+ +------!
45 ! +-----------+
47 ! +------+ <- CAIF Core Protocol
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-info`` mechanism enables device drivers to report device
10 The original motivation for the ``devlink-info`` API was twofold:
12 - making it possible to automate device and firmware management in a fleet
13 of machines in a vendor-independent fashion (see also
14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`);
15 - name the per component FW versions (as opposed to the crowded ethtool
18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver
19 versions is generally discouraged - here, and via any other Linux API.
21 .. list-table:: List of top level info objects
[all …]
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 18 -----
23 Usage: gendwarfksyms [options] elf-object-file ... < symbol-list
26 -d, --debug Print debugging information
27 --dump-dies Dump DWARF DIE contents
28 --dump-die-map Print debugging information about die_map changes
29 --dump-types Dump type strings
30 --dump-versions Dump expanded type strings used for symbol versions
31 -s, --stable Support kABI stability features
32 -T, --symtypes file Write a symtypes file
33 -h, --help Print this message
[all …]
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
39 existing features like key derivation can be utilized. It should however also
44 ----------------
50 addition, it deals with flash-specific wear-leveling and transparent I/O error
60 +------------+ +*******+ +-----------+ +-----+
[all …]
|
| D | mount_api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
37 (3) Validate and pre-process the context.
52 The first is invoked to set up the filesystem-specific parts of a filesystem
93 below). This must be set by the ->init_fs_context() file_system_type
115 superblock thereof). This is filled in by the ->get_tree() op. If this
116 is set, an active reference on root->d_sb must also be held.
174 These will be bitwise-OR'd with s->s_iflags when a superblock is created.
186 FS_CONTEXT_FOR_RECONFIGURE Change an existing mount
228 Called to clean up the filesystem-specific part of the filesystem context
229 when the context is destroyed. It should be aware that parts of the
[all …]
|
| /Documentation/watchdog/ |
| D | watchdog-api.rst | 9 Copyright 2002 Christer Weingel <wingel@nano-system.com>
11 Some parts of this document are copied verbatim from the sbc60xxwdt
32 The Linux watchdog API is a rather ad-hoc construction and different
33 drivers implement different, and sometimes incompatible, parts of it.
34 This file is an attempt to document the existing usage and allow
45 like this source file: see samples/watchdog/watchdog-simple.c
71 cause a reboot if the watchdog is not re-opened in sufficient time.
217 under and one over both bits will be set - this may seem odd but makes
271 [FIXME -- better explanations]
|
1234