| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_ttm.h | 1 /* SPDX-License-Identifier: MIT */
13 * i915_gem_to_ttm - Convert a struct drm_i915_gem_object to a
22 return &obj->__do_not_access; in i915_gem_to_ttm()
31 * i915_ttm_is_ghost_object - Check if the ttm bo is a ghost object.
39 return bo->destroy != i915_ttm_bo_destroy; in i915_ttm_is_ghost_object()
43 * i915_ttm_to_gem - Convert a struct ttm_buffer_object to an embedding
82 * i915_ttm_gtt_binds_lmem - Should the memory be viewed as LMEM by the GTT?
85 * Return: true if memory should be viewed as LMEM for GTT binding purposes,
90 return mem->mem_type != I915_PL_SYSTEM; in i915_ttm_gtt_binds_lmem()
94 * i915_ttm_cpu_maps_iomem - Should the memory be viewed as IOMEM by the CPU?
[all …]
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | dma-mapping.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
24 * arm_dma_alloc - allocate consistent memory for DMA
25 * @dev: valid struct device pointer, or NULL for ISA and EISA-like devices
27 * @handle: bus-specific DMA address
31 * allocates pages, and will return the CPU-viewed address, and sets @handle
32 * to be the device-viewed address.
38 * arm_dma_free - free memory allocated by arm_dma_alloc
39 * @dev: valid struct device pointer, or NULL for ISA and EISA-like devices
41 * @cpu_addr: CPU-view address returned from dma_alloc_coherent
42 * @handle: device-view address returned from dma_alloc_coherent
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | perf-timechart.txt | 1 perf-timechart(1)
5 ----
6 perf-timechart - Tool to visualize total system behavior during a workload
9 --------
14 -----------
19 and CPU events (task switches, running times, CPU power states, etc),
20 but it's possible to record IO (disk, network) activity using -I argument.
23 that can be viewed with popular SVG viewers such as 'Inkscape'. Depending
24 on the events in the perf.data file, timechart will contain scheduler/cpu
34 -----------------
[all …]
|
| D | perf-arm-spe.txt | 1 perf-arm-spe(1)
5 ----
6 perf-arm-spe - Support for Arm Statistical Profiling Extension within Perf tools
9 --------
11 'perf record' -e arm_spe//
14 -----------
17 events down to individual instructions. Rather than being interrupt-driven, it picks an
33 architectural instructions or all micro-ops. Sampling happens at a programmable interval. The
35 sample. This minimum interval is used by the driver if no interval is specified. A pseudo-random
62 ----------------
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-timechart.txt | 1 perf-timechart(1)
5 ----
6 perf-timechart - Tool to visualize total system behavior during a workload
9 --------
14 -----------
19 and CPU events (task switches, running times, CPU power states, etc),
20 but it's possible to record IO (disk, network) activity using -I argument.
23 that can be viewed with popular SVG viewers such as 'Inkscape'. Depending
24 on the events in the perf.data file, timechart will contain scheduler/cpu
34 -----------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/bus/ |
| D | socionext,uniphier-system-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/bus/socionext,uniphier-system-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The UniPhier System Bus is an external bus that connects on-board devices to
11 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
16 within each bank to the CPU-viewed address. The needed setup includes the
21 - Masahiro Yamada <yamada.masahiro@socionext.com>
25 const: socionext,uniphier-system-bus
30 "#address-cells":
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/bus/ |
| D | socionext,uniphier-system-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/bus/socionext,uniphier-system-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The UniPhier System Bus is an external bus that connects on-board devices to
11 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
16 within each bank to the CPU-viewed address. The needed setup includes the
21 - Masahiro Yamada <yamada.masahiro@socionext.com>
25 const: socionext,uniphier-system-bus
30 "#address-cells":
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | numa.rst | 19 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
20 of the system--although some components necessary for a stand-alone SMP system
22 connected together with some sort of system interconnect--e.g., a crossbar or
23 point-to-point link are common types of NUMA system interconnects. Both of
29 to and accessible from any CPU attached to any cell and cache coherency
33 away the cell containing the CPU or IO bus making the memory access is from the
43 [cache misses] to be to "local" memory--memory on the same cell, if any--or
53 "closer" nodes--nodes that map to closer cells--will generally experience
65 the existing nodes--or the system memory for non-NUMA platforms--into multiple
68 application features on non-NUMA platforms, and as a sort of memory resource
[all …]
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | numa.rst | 17 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
18 of the system--although some components necessary for a stand-alone SMP system
20 connected together with some sort of system interconnect--e.g., a crossbar or
21 point-to-point link are common types of NUMA system interconnects. Both of
27 to and accessible from any CPU attached to any cell and cache coherency
31 away the cell containing the CPU or IO bus making the memory access is from the
41 [cache misses] to be to "local" memory--memory on the same cell, if any--or
51 "closer" nodes--nodes that map to closer cells--will generally experience
63 the existing nodes--or the system memory for non-NUMA platforms--into multiple
66 application features on non-NUMA platforms, and as a sort of memory resource
[all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/rockchip/ |
| D | rk3328-a1.dts | 1 // SPDX-License-Identifier: (GPL-2.0-only OR MIT)
2 // Copyright (c) 2017-2019 Arm Ltd.
4 /dts-v1/;
9 compatible = "azw,beelink-a1", "rockchip,rk3328";
17 * UART pins, as viewed with bottom of case removed:
20 * /-------
21 * L / o <- Gnd
22 * e / o <-- Rx
23 * f / o <--- Tx
24 * t / o <---- +3.3v
[all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/rockchip/ |
| D | rk3328-a1.dts | 1 // SPDX-License-Identifier: (GPL-2.0-only OR MIT)
2 // Copyright (c) 2017-2019 Arm Ltd.
4 /dts-v1/;
9 compatible = "azw,beelink-a1", "rockchip,rk3328";
12 * UART pins, as viewed with bottom of case removed:
15 * /-------
16 * L / o <- Gnd
17 * e / o <-- Rx
18 * f / o <--- Tx
19 * t / o <---- +3.3v
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/hyperv/ |
| D | vmbus.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 VMbus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
11 and the synthetic device implementation that is part of Hyper-V, and
12 signaling primitives to allow Hyper-V and the guest to interrupt
17 establishes the VMbus control path with the Hyper-V host, then
21 Most synthetic devices offered by Hyper-V have a corresponding Linux
29 * PCI device pass-thru
34 * Key/Value Pair (KVP) exchange with Hyper-V
35 * Hyper-V online backup (a.k.a. VSS)
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | percpu-refcount.c | 1 // SPDX-License-Identifier: GPL-2.0-only
8 #include <linux/percpu-refcount.h>
12 * don't try to detect the ref hitting 0 - which means that get/put can just
14 * particular cpu can (and will) wrap - this is fine, when we go to shutdown the
23 * the ref hitting 0 on every put - this would require global synchronization
36 #define PERCPU_COUNT_BIAS (1LU << (BITS_PER_LONG - 1))
44 (ref->percpu_count_ptr & ~__PERCPU_REF_ATOMIC_DEAD); in percpu_count_ptr()
48 * percpu_ref_init - initialize a percpu refcount
59 * Note that @release must not sleep - it may potentially be called from RCU
70 ref->percpu_count_ptr = (unsigned long) in percpu_ref_init()
[all …]
|
| /kernel/linux/linux-6.6/lib/ |
| D | percpu-refcount.c | 1 // SPDX-License-Identifier: GPL-2.0-only
9 #include <linux/percpu-refcount.h>
13 * don't try to detect the ref hitting 0 - which means that get/put can just
15 * particular cpu can (and will) wrap - this is fine, when we go to shutdown the
24 * the ref hitting 0 on every put - this would require global synchronization
37 #define PERCPU_COUNT_BIAS (1LU << (BITS_PER_LONG - 1))
45 (ref->percpu_count_ptr & ~__PERCPU_REF_ATOMIC_DEAD); in percpu_count_ptr()
49 * percpu_ref_init - initialize a percpu refcount
60 * Note that @release must not sleep - it may potentially be called from RCU
71 ref->percpu_count_ptr = (unsigned long) in percpu_ref_init()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 10 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
16 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
19 programming interface that a NUMA-aware application can take advantage of. When
28 ------------------------
41 not to overload the initial boot node with boot-time
45 this is an optional, per-task policy. When defined for a
61 In a multi-threaded task, task policies apply only to the thread
98 mapping-- i.e., at Copy-On-Write.
101 virtual address space--a.k.a. threads--independent of when
106 are NOT inheritable across exec(). Thus, only NUMA-aware
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/coresight/ |
| D | coresight-config.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 programming of the CoreSight system with pre-defined configurations that
17 Many CoreSight components can be programmed in complex ways - especially ETMs.
30 --------
41 accesses in the driver - the resource usage and parameter descriptions
67 system - which is described below.
74 --------------
82 enabled on a class of devices - i.e. any ETMv4, or specific devices, e.g. a
118 perf record -e cs_etm/autofdo/ myapp
137 system can be viewed using the configfs API.
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/probes/ |
| D | decode.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
32 /* We need a run-time check to determine str_pc_offset */
41 long cpsr = regs->ARM_cpsr; in bx_write_pc()
49 regs->ARM_cpsr = cpsr; in bx_write_pc()
50 regs->ARM_pc = pcv; in bx_write_pc()
62 /* We need run-time testing to determine if load_write_pc() should interwork. */
73 regs->ARM_pc = pcv; in load_write_pc()
90 /* We could be an ARMv6 binary on ARMv7 hardware so we need a run-time check. */
101 regs->ARM_pc = pcv; in alu_write_pc()
118 * viewed as an array of these and declared like:
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/probes/ |
| D | decode.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
32 /* We need a run-time check to determine str_pc_offset */
41 long cpsr = regs->ARM_cpsr; in bx_write_pc()
49 regs->ARM_cpsr = cpsr; in bx_write_pc()
50 regs->ARM_pc = pcv; in bx_write_pc()
62 /* We need run-time testing to determine if load_write_pc() should interwork. */
73 regs->ARM_pc = pcv; in load_write_pc()
90 /* We could be an ARMv6 binary on ARMv7 hardware so we need a run-time check. */
101 regs->ARM_pc = pcv; in alu_write_pc()
118 * viewed as an array of these and declared like:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 12 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
18 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
21 programming interface that a NUMA-aware application can take advantage of. When
30 ------------------------
43 not to overload the initial boot node with boot-time
47 this is an optional, per-task policy. When defined for a
63 In a multi-threaded task, task policies apply only to the thread
100 mapping-- i.e., at Copy-On-Write.
103 virtual address space--a.k.a. threads--independent of when
108 are NOT inheritable across exec(). Thus, only NUMA-aware
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ |
| D | memory-barriers.txt | 19 documentation at tools/memory-model/. Nevertheless, even this memory
20 model should be viewed as the collective opinion of its maintainers rather
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | memory-barriers.txt | 19 documentation at tools/memory-model/. Nevertheless, even this memory
20 model should be viewed as the collective opinion of its maintainers rather
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Data dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | dsa.rst | 22 An Ethernet switch typically comprises multiple front-panel ports and one
23 or more CPU or management ports. The DSA subsystem currently relies on the
27 gateways, or even top-of-rack switches. This host Ethernet controller will
28 be later referred to as "master" and "cpu" in DSA terminology and code.
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
[all …]
|
| /kernel/linux/linux-6.6/drivers/media/pci/cx18/ |
| D | cx23418.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
11 #include <media/drv-intf/cx2341x.h>
19 IN[0] - Task ID. This is one of the XPU_CMD_MASK_YYY where XPU is
21 OUT[0] - Task handle. This handle is passed along with commands to
23 ReturnCode - One of the ERR_SYS_... */
27 IN[0] - Task handle. Hanlde of the task to destroy
28 ReturnCode - One of the ERR_SYS_... */
31 /* All commands for CPU have the following mask set */
49 IN[0] - audio parameters (same as CX18_CPU_SET_AUDIO_PARAMETERS?)
50 IN[1] - caller buffer address, or 0
[all …]
|