| /kernel/linux/linux-4.19/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-4.19/arch/arm/include/asm/ |
| D | dma-mapping.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
9 #include <linux/dma-debug.h>
30 * functions used internally by the DMA-mapping API to provide DMA
37 pfn -= dev->dma_pfn_offset; in pfn_to_dma()
46 pfn += dev->dma_pfn_offset; in dma_to_pfn()
95 return dma_to_pfn(dev, *dev->dma_mask); in dma_max_pfn()
109 return dev->archdata.dma_coherent; in is_device_dma_coherent()
113 * arm_dma_alloc - allocate consistent memory for DMA
114 * @dev: valid struct device pointer, or NULL for ISA and EISA-like devices
116 * @handle: bus-specific DMA address
[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-4.19/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-4.19/Documentation/devicetree/bindings/bus/ |
| D | uniphier-system-bus.txt | 3 The UniPhier System Bus is an external bus that connects on-board devices to
4 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
9 within each bank to the CPU-viewed address. The needed setup includes the base
14 - compatible: should be "socionext,uniphier-system-bus".
15 - reg: offset and length of the register set for the bus controller device.
16 - #address-cells: should be 2. The first cell is the bank number (chip select).
18 - #size-cells: should be 1.
19 - ranges: should provide a proper address translation from the System Bus to
24 defined. Some SoCs can use 0x00000000-0x0fffffff and 0x40000000-0x4fffffff,
25 while other SoCs can only use 0x40000000-0x4fffffff. There might be additional
[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-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-4.19/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-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-4.19/lib/ |
| D | percpu-refcount.c | 6 #include <linux/percpu-refcount.h>
10 * don't try to detect the ref hitting 0 - which means that get/put can just
12 * particular cpu can (and will) wrap - this is fine, when we go to shutdown the
21 * the ref hitting 0 on every put - this would require global synchronization
34 #define PERCPU_COUNT_BIAS (1LU << (BITS_PER_LONG - 1))
42 (ref->percpu_count_ptr & ~__PERCPU_REF_ATOMIC_DEAD); in percpu_count_ptr()
46 * percpu_ref_init - initialize a percpu refcount
56 * Note that @release must not sleep - it may potentially be called from RCU
66 ref->percpu_count_ptr = (unsigned long) in percpu_ref_init()
68 if (!ref->percpu_count_ptr) in percpu_ref_init()
[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-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-4.19/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 12 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
18 (``Documentation/cgroup-v1/cpusets.txt``)
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-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-4.19/Documentation/filesystems/caching/ |
| D | fscache.txt | 12 FS-Cache mediates between cache backends (such as CacheFS) and network
15 +---------+
16 | | +--------------+
17 | NFS |--+ | |
18 | | | +-->| CacheFS |
19 +---------+ | +----------+ | | /dev/hda5 |
20 | | | | +--------------+
21 +---------+ +-->| | |
22 | | | |--+
23 | AFS |----->| FS-Cache |
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/drivers/media/pci/cx18/ |
| D | cx23418.h | 20 #include <media/drv-intf/cx2341x.h>
28 IN[0] - Task ID. This is one of the XPU_CMD_MASK_YYY where XPU is
30 OUT[0] - Task handle. This handle is passed along with commands to
32 ReturnCode - One of the ERR_SYS_... */
36 IN[0] - Task handle. Hanlde of the task to destroy
37 ReturnCode - One of the ERR_SYS_... */
40 /* All commands for CPU have the following mask set */
58 IN[0] - audio parameters (same as CX18_CPU_SET_AUDIO_PARAMETERS?)
59 IN[1] - caller buffer address, or 0
60 ReturnCode - ??? */
[all …]
|
| /kernel/linux/linux-4.19/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-5.10/arch/arm/probes/ |
| D | decode.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
31 /* We need a run-time check to determine str_pc_offset */
55 it |= it >> (27 - 10); /* Carry ITSTATE<2> to correct place */ in it_advance()
65 long cpsr = regs->ARM_cpsr; in bx_write_pc()
73 regs->ARM_cpsr = cpsr; in bx_write_pc()
74 regs->ARM_pc = pcv; in bx_write_pc()
86 /* We need run-time testing to determine if load_write_pc() should interwork. */
97 regs->ARM_pc = pcv; in load_write_pc()
114 /* We could be an ARMv6 binary on ARMv7 hardware so we need a run-time check. */
125 regs->ARM_pc = pcv; in alu_write_pc()
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/probes/ |
| D | decode.h | 39 /* We need a run-time check to determine str_pc_offset */
63 it |= it >> (27 - 10); /* Carry ITSTATE<2> to correct place */ in it_advance()
73 long cpsr = regs->ARM_cpsr; in bx_write_pc()
81 regs->ARM_cpsr = cpsr; in bx_write_pc()
82 regs->ARM_pc = pcv; in bx_write_pc()
94 /* We need run-time testing to determine if load_write_pc() should interwork. */
105 regs->ARM_pc = pcv; in load_write_pc()
122 /* We could be an ARMv6 binary on ARMv7 hardware so we need a run-time check. */
133 regs->ARM_pc = pcv; in alu_write_pc()
150 * viewed as an array of these and declared like:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 For the aQuantia Multi-Gigabit PCI Express Family of Ethernet Adapters
12 - Identifying Your Adapter
13 - Configuration
14 - Supported ethtool options
15 - Command Line Parameters
16 - Config file parameters
17 - Support
18 - License
23 The driver in this release is compatible with AQC-100, AQC-107, AQC-108
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
36 - Minimalist, so it's easier to support new device controller hardware.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
36 - Minimalist, so it's easier to support new device controller hardware.
[all …]
|