A\-side (full) in projects: Linux-v6.1 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:a +full:- +full:side (Results 1 – 25 of 1053) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...43

/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
D	fsl,mu-msi.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Frank Li <Frank.Li@nxp.com> 16 for one processor (A side) to signal the other processor (B side) using 20 different clocks (from each side of the different peripheral buses). 21 Therefore, the MU must synchronize the accesses from one side to the 23 registers (Processor A-side, Processor B-side). 28 - $ref: /schemas/interrupt-controller/msi-controller.yaml# [all …]
/Linux-v6.1/drivers/char/hw_random/
D	Kconfig	1 # SPDX-License-Identifier: GPL-2.0-only 12 To compile this driver as a module, choose M here: the 13 module will be called rng-core. This provides a device 28 This driver provides kernel-side support for a generic Random 29 Number Generator used by reading a 'dumb' iomem address that 30 is to be read no faster than, for example, once a second; 31 the default FPGA bitstream on the TS-7800 has such functionality. 33 To compile this driver as a module, choose M here: the 34 module will be called timeriomem-rng. 43 This driver provides kernel-side support for the Random Number [all …]
/Linux-v6.1/Documentation/locking/
D	seqlock.rst	8 Sequence counters are a reader-writer consistency mechanism with 9 lockless readers (read-only retry loops), and no writer starvation. They 11 reader wants a consistent set of information and is willing to retry if 14 A data set is consistent when the sequence count at the beginning of the 15 read side critical section is even and the same sequence count value is 17 be copied out inside the read side critical section. If the sequence 24 the end of the write side critical section the sequence count becomes 27 A sequence counter write side critical section must never be preempted 28 or interrupted by read side sections. Otherwise the reader will spin for 30 interrupted writer. If that reader belongs to a real-time scheduling [all …]
/Linux-v6.1/Documentation/usb/
D	gadget_serial.rst	`7 (updated 8-May-2008 for v2.3) 11 ---------------------- 19 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 22 You should have received a copy of the GNU General Public 25 MA 02111-1307 USA. 35 ------------- 38 version 2.3 or later of the gadget serial driver in a 2.6 55 -------- 56 The gadget serial driver is a Linux USB gadget driver, a USB device 57 side driver. It runs on a Linux system that has USB device side [all …]`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/silvermont/
D	virtual-memory.json	13 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)", 17 … cycle when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk im… 22 "BriefDescription": "Duration of D-side page-walks in core cycles", 26 … when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by numbe… 31 "BriefDescription": "D-side page-walks", 36 …cDescription": "This event counts when a data (D) page walk is completed or started. Since a page… 41 "BriefDescription": "Duration of I-side page-walks in core cycles", 45 …a I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided … 50 "BriefDescription": "I-side page-walks", 55 …when an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, … [all …]
/Linux-v6.1/Documentation/RCU/
D	checklist.rst	1 .. SPDX-License-Identifier: GPL-2.0 8 This document contains a checklist for producing and reviewing patches 10 result in the same sorts of problems that leaving out a locking primitive 12 over a rather long period of time, but improvements are always welcome! 14 0. Is RCU being applied to a read-mostly situation? If the data 18 tool for the job. Yes, RCU does reduce read-side overhead by 19 increasing write-side overhead, which is exactly why normal uses 23 provides a simpler implementation. An example of this situation 27 Yet another exception is where the low real-time latency of RCU's 28 read-side primitives is critically important. [all …]
D	whatisRCU.rst	3 What is RCU? -- "Read, Copy, Update" 22 RCU is a synchronization mechanism that was added to the Linux kernel 23 during the 2.5 development effort that is optimized for read-mostly 25 getting there can sometimes be a challenge. Part of the problem is that 42 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>` 50 People who prefer starting with a conceptual overview should focus on 62 everything, feel free to read the whole thing -- but if you are really 64 never need this document anyway. ;-) 69 ---------------- 73 within a data structure (possibly by replacing them with references to [all …]
D	lockdep.rst	1 .. SPDX-License-Identifier: GPL-2.0 8 aware of when each task enters and leaves any flavor of RCU read-side 18 rcu_read_lock_bh_held() for RCU-bh. 19 rcu_read_lock_sched_held() for RCU-sched. 27 In addition, a separate kernel config parameter CONFIG_PROVE_RCU enables 31 Check for RCU read-side critical section. 33 Check for RCU-bh read-side critical section. 35 Check for RCU-sched read-side critical section. 37 Check for SRCU read-side critical section. 45 is invoked by both RCU-bh readers and updaters. [all …]
/Linux-v6.1/Documentation/RCU/Design/Requirements/
D	Requirements.rst	2 A Tour Through RCU's Requirements 16 ------------ 18 Read-copy update (RCU) is a synchronization mechanism that is often used 19 as a replacement for reader-writer locking. RCU is unusual in that 20 updaters do not block readers, which means that RCU's read-side 28 thought of as an informal, high-level specification for RCU. It is 32 has this learning process been a lot of fun, but it has also been a 40 #. `Fundamental Non-Requirements`_ 42 #. `Quality-of-Implementation Requirements`_ 44 #. `Software-Engineering Requirements`_ [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/powerpc/power9/
D	translation.json	15 …che was reloaded with Shared (S) data from another core's L2 on the same chip due to a demand load" 20 "BriefDescription": "Double-Precion or Quad-Precision instruction completed" 25 …escription": "A Page Table Entry was loaded into the TLB from another chip's memory on the same No… 35 …A Page Table Entry was loaded into the TLB with Shared (S) data from another chip's L2 or L3 on th… 45 …"BriefDescription": "Finish stall due to a vector fixed point instruction in the execution pipelin… 50 "BriefDescription": "LSU Finished a PPC instruction (up to 4 per cycle)" 60 …A Page Table Entry was loaded into the TLB with Shared (S) data from another chip's L2 or L3 on a … 65 …"BriefDescription": "Completion stall due to a long latency vector fixed point instruction (divisi… 70 …on": "The processor's data cache was reloaded from a location other than the local core's L2 due t… 75 …n": "A Page Table Entry was loaded into the TLB either shared or modified data from another core's… [all …]
D	pipeline.json	10 "BriefDescription": "Number of I-ERAT reloads" 15 …te that this count is per slice, so if a load spans multiple slices this event will increment mult… 25 …"BriefDescription": "Finish stall because the NTF instruction was a multi-cycle instruction issued… 30 …ded either shared or modified data from another core's L2/L3 on the same chip due to a marked load" 35 …ription": "A Page Table Entry was loaded into the TLB from another chip's L4 on a different Node o… 40 …"BriefDescription": "A Page Table Entry was loaded into the TLB from local core's L2 without confl… 80 …ription": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core's L… 90 …r's data cache was reloaded from another chip's L4 on a different Node or Group (Distant) due to a… 95 …escription": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core'… 100 …rbitration onto the issue pipe to another instruction (from the same thread or a different thread)" [all …]
D	marked.json	5 …"BriefDescription": "Number of cycles the marked instruction is experiencing a stall while it is n… 10 …"BriefDescription": "A Page Directory Entry was reloaded to a level 1 page walk cache from beyond … 20 …Description": "A Page Table Entry was loaded into the TLB with Shared (S) data from another core's… 25 …e was reloaded from another chip's memory on the same Node or Group ( Remote) due to a demand load" 45 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's … 50 …"BriefDescription": "A Page Table Entry was reloaded to a level 3 page walk cache from the core's … 60 …"BriefDescription": "A Page Table Entry was loaded into the TLB from the local chip's L4 cache due… 70 …iption": "A Page Table Entry was loaded into the TLB with Shared (S) data from another core's ECO … 85 …he processor's Instruction cache was reloaded from a location other than the local core's L3 due t… 95 …ption": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core's ECO… [all …]
D	other.json	30 "BriefDescription": "IERAT reloaded (after a miss) for 4K pages" 45 …on": "The processor's data cache was reloaded from a location other than the local core's L3 due t… 50 …cription": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core's … 55 …"BriefDescription": "A Conditional Branch that resolved to taken was mispredicted as not taken (du… 60 …"BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The strea… 65 "BriefDescription": "Read-write data cache collisions" 80 …"BriefDescription": "Cycles in which no new instructions can be dispatched to the ICT after a flus… 85 …"BriefDescription": "A radix translation attempt missed in the TLB and all levels of page walk cac… 90 "BriefDescription": "D-cache invalidates sent over the reload bus to the core" 120 …"BriefDescription": "L3 TM CAM is full when a L2 castout of TM_SC line occurs. Line is pushed to … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/powerpc/power8/
D	frontend.json	5 …"BriefDescription": "Branch instruction completed with a target address less than current instruct… 41 "BriefDescription": "Cycles when a demand ifetch was pending", 47 "BriefDescription": "Number of I-ERAT reloads", 53 "BriefDescription": "IERAT Reloaded (Miss) for a 16M page", 60 "PublicDescription": "IERAT Reloaded (Miss) for a 4k page" 65 "BriefDescription": "IERAT Reloaded (Miss) for a 64k page", 89 …n cache was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Gr… 90 …n cache was reloaded with Modified (M) data from another chip's L2 or L3 on a different Node or Gr… 95 …ion cache was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Gr… 96 …ion cache was reloaded with Shared (S) data from another chip's L2 or L3 on a different Node or Gr… [all …]
/Linux-v6.1/drivers/block/rnbd/
D	README	`6 ------------ 8 RNBD (RDMA Network Block Device) is a pair of kernel modules 9 (client and server) that allow for remote access of a block device on 12 on the client side as local block devices. 19 ------------ 24 ----------- 26 Server side: 29 Client side: 32 /sys/devices/virtual/rnbd-client/ctl/map_device 34 Where "sessname=" is a session name, a string to identify the session [all …]`
/Linux-v6.1/include/linux/
D	seqlock.h	1 /* SPDX-License-Identifier: GPL-2.0 / 6 seqcount_t / seqlock_t - a reader-writer consistency mechanism with 7 * lockless readers (read-only retry loops), and no writer starvation. 12 * - Based on x86_64 vsyscall gettimeofday: Keith Owens, Andrea Arcangeli 13 * - Sequence counters with associated locks, (C) 2020 Linutronix GmbH 17 #include <linux/kcsan-checks.h> 26 * The seqlock seqcount_t interface does not prescribe a precise sequence of 27 * read begin/retry/end. For readers, typically there is a call to 31 * As a consequence, we take the following best-effort approach for raw usage 32 * via seqcount_t under KCSAN: upon beginning a seq-reader critical section, [all …]
D	srcu.h	1 /* SPDX-License-Identifier: GPL-2.0+ / 3 Sleepable Read-Copy Update mechanism for mutual exclusion 11 * For detailed explanation of Read-Copy Update mechanism see - 76 * srcu_read_lock_held - might we be in SRCU read-side critical section? 80 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC, 81 * this assumes we are in an SRCU read-side critical section unless it can 95 return lock_is_held(&ssp->dep_map); in srcu_read_lock_held() 108 * srcu_dereference_check - fetch SRCU-protected pointer for later dereferencing 111 * really are in an SRCU read-side critical section. 112 * @c: condition to check for update-side use [all …]
D	rcupdate.h	1 /* SPDX-License-Identifier: GPL-2.0+ / 3 Read-Copy Update mechanism for mutual exclusion 15 * For detailed explanation of Read-Copy Update mechanism see - 34 #define ULONG_CMP_GE(a, b) (ULONG_MAX / 2 >= (a) - (b)) argument 35 #define ULONG_CMP_LT(a, b) (ULONG_MAX / 2 < (a) - (b)) argument 36 #define ulong2long(a) ((long )(&(a))) argument 37 #define USHORT_CMP_GE(a, b) (USHRT_MAX / 2 >= (unsigned short)((a) - (b))) argument 38 #define USHORT_CMP_LT(a, b) (USHRT_MAX / 2 < (unsigned short)((a) - (b))) argument 51 // not-yet-completed RCU grace periods. 55 * same_state_synchronize_rcu - Are two old-state values identical? [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
D	uncore-cache.json	15 …a user to capture occupancy related information by filtering the Cb0 occupancy count captured in C… 24 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 34 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 44 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 54 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 64 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa… 74 …"PublicDescription": "Counts the number of lines that were victimized on a fill. This can be filt… 84 …"PublicDescription": "Counts the number of lines that were victimized on a fill. This can be filt… 94 …"PublicDescription": "Counts the number of lines that were victimized on a fill. This can be filt… 104 …"PublicDescription": "Counts the number of lines that were victimized on a fill. This can be filt… [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/knightslanding/
D	virtual-memory.json	3 "BriefDescription": "Counts the number of load micro-ops retired that cause a DTLB miss", 17 …"PublicDescription": "This event counts every cycle when a data (D) page walk or instruction (I) p… 22 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc… 30 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa… 39 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc… 43 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe… 48 "BriefDescription": "Counts the total I-side page walks that are completed.", 57 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
/Linux-v6.1/drivers/char/ipmi/
D	Kconfig	1 # SPDX-License-Identifier: GPL-2.0-only 7 tristate 'IPMI top-level message handler' 14 IPMI is a standard for managing sensors (temperature, 15 voltage, etc.) in a system. 17 See <file:Documentation/driver-api/ipmi.rst> for more details on the driver. 31 bool 'Generate a panic event to all BMCs on a panic' 33 When a panic occurs, this will cause the IPMI message handler to, 44 When a panic occurs, this will cause the IPMI message handler to, 46 address of the panic generator (byte 4 of the event), a sequence 66 Provides a driver for System Interfaces (KCS, SMIC, BT). [all …]
/Linux-v6.1/Documentation/devicetree/bindings/memory-controllers/
D	rockchip,rk3399-dmc.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/rockchip,rk3399-dmc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Brian Norris <briannorris@chromium.org> 15 - rockchip,rk3399-dmc 17 devfreq-events: 21 Documentation/devicetree/bindings/devfreq/event/rockchip-dfi.txt. 26 clock-names: 28 - const: dmc_clk [all …]`
/Linux-v6.1/Documentation/driver-api/usb/
D	gadget.rst	11 This document presents a Linux-USB "Gadget" kernel mode API, for use 13 an overview of the API structure, and shows how that fits into a system 15 address a number of important problems, including: 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 [all …]
/Linux-v6.1/drivers/infiniband/ulp/rtrs/
D	README	5 RTRS (RDMA Transport) is a reliable high speed transport library 11 possibility to either write data from an sg list to the remote side 12 or to request ("read") data transfer from the remote side into a given 15 RTRS provides I/O fail-over and load-balancing capabilities by using 17 Documentation/ABI/testing/sysfs-class-rtrs-client). 26 -------- 27 An established connection between a client and a server is called rtrs 28 session. A session is associated with a set of memory chunks reserved on the 29 server side for a given client for rdma transfer. A session 30 consists of multiple paths, each representing a separate physical link [all …]
/Linux-v6.1/Documentation/driver-api/
D	io-mapping.rst	8 The io_mapping functions in linux/io-mapping.h provide an abstraction for 10 usage is to support the large graphics aperture on 32-bit processors where 14 A mapping object is created during driver initialization using:: 20 mappable, while 'size' indicates how large a mapping region to 23 This _wc variant provides a mapping which may only be used with 40 undefined result. The return value points to a single page in CPU address 43 This _wc variant returns a write-combining map to the page and may only be 49 io_mapping_map_local_wc() has a side effect on X86 32bit as it disables 50 migration to make the mapping code work. No caller can rely on this side 53 io_mapping_map_atomic_wc() has the side effect of disabling preemption and [all …]

12 3 4 5 6 7 8 9 10 >>...43