Searched +full:side +full:- +full:by +full:- +full:side (Results 1 – 25 of 379) sorted by relevance
12345678910>>...16
| /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>
14 communicate and coordinate by passing messages (e.g. data, status
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).
[all …]
|
| /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
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
43 multiple writers. Write side critical sections must thus be serialized
44 by an external lock.
[all …]
|
| /Documentation/RCU/ |
| 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.
20 rcu_read_lock_any_held() for any of normal RCU, RCU-bh, and RCU-sched.
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
43 invoked by both RCU readers and updaters.
[all …]
|
| D | checklist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
27 Yet another exception is where the low real-time latency of RCU's
28 read-side primitives is critically important.
33 counter-intuitive situation where rcu_read_lock() and
49 them -- even x86 allows later loads to be reordered to precede
54 relating to itself that other tasks can read, there by definition
59 2. Do the RCU read-side critical sections make proper use of
[all …]
|
| D | whatisRCU.rst | 3 What is RCU? -- "Read, Copy, Update"
21 …ries: Fundamentals https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries
22 …Cases https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries-additional-use-cases
28 during the 2.5 development effort that is optimized for read-mostly
47 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>`
56 Section 1, though most readers will profit by reading this section at
61 into the kernel source code. People who reason best by analogy should
67 everything, feel free to read the whole thing -- but if you are really
69 never need this document anyway. ;-)
74 ----------------
[all …]
|
| D | lockdep-splat.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Lockdep-RCU Splat
7 Lockdep-RCU was added to the Linux kernel in early 2010
10 family to access an RCU-protected pointer without the proper protection.
11 When such misuse is detected, an lockdep-RCU splat is emitted.
13 The usual cause of a lockdep-RCU splat is someone accessing an
14 RCU-protected data structure without either (1) being in the right kind of
15 RCU read-side critical section or (2) holding the right update-side lock.
20 So let's look at an example RCU lockdep splat from 3.0-rc5, one that
25 -----------------------------
[all …]
|
| D | rcu.rst | 6 The basic idea behind RCU (read-copy update) is to split destructive
11 since dropped their references. For example, an RCU-protected deletion
17 --------------------------
19 - Why would anyone want to use RCU?
21 The advantage of RCU's two-part approach is that RCU readers need
26 in read-mostly situations. The fact that RCU readers need not
27 acquire locks can also greatly simplify deadlock-avoidance code.
29 - How can the updater tell when a grace period has completed
33 block, switch to user-mode execution, or enter the idle loop.
36 read-side critical sections. So, if we remove an item from a
[all …]
|
| D | UP.rst | 16 --------------------------
18 Suppose that an RCU-based algorithm scans a linked list containing
20 this same list in softirq context. Suppose that the process-context scan
21 is referencing element B when it is interrupted by softirq processing,
33 Example 2: Function-Call Fatality
34 ---------------------------------
37 by having call_rcu() directly invoke its arguments only if it was called
40 Suppose that an RCU-based algorithm again scans a linked list containing
49 all RCU read-side critical sections currently executing have completed.
56 Example 3: Death by Deadlock
[all …]
|
| /Documentation/usb/ |
| D | gadget_serial.rst | 7 (updated 8-May-2008 for v2.3)
11 ----------------------
14 published by the Free Software Foundation; either version 2 of
25 MA 02111-1307 USA.
28 Copyright (C) 2004 by Al Borchers (alborchers@steinerpoint.com).
35 -------------
55 --------
57 side driver. It runs on a Linux system that has USB device side
65 --------------------------------------
66 | Host-Side CDC ACM USB Host |
[all …]
|
| /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
43 This _wc variant returns a write-combining map to the page and may only be
44 used with mappings created by io_mapping_create_wc()
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
70 'vaddr' must be the value returned by the last io_mapping_map_local_wc() or
72 undoes the side effects of the mapping functions.
80 This works like io_mapping_map_atomic/local_wc() except it has no side
|
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
12 additional chipselect line is usually active-low (nCS); four signals are
18 only "master" side interfaces are supported, where Linux talks to SPI
25 a pair of FIFOs connected to dual DMA engines on the other side of the
28 the SPI side of their device as a :c:type:`struct spi_controller
32 <spi_board_info>` descriptors which are usually provided by
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
52 .. kernel-doc:: drivers/spi/spi.c
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 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
40 #. `Fundamental Non-Requirements`_
42 #. `Quality-of-Implementation Requirements`_
44 #. `Software-Engineering Requirements`_
48 This is followed by a summary_, however, the answers to
53 ------------------------
[all …]
|
| /Documentation/staging/ |
| D | speculation.rst | 8 ------------------------------------------------------------------------------
17 absence of data in caches. Such state may form side-channels which can be
21 checks to be ignored by code which is speculatively executed. Consider the
42 It is possible that a CPU mis-predicts the conditional branch, and
62 of an out-of-bounds address, while the second call will influence
67 Mitigating speculation side-channels
71 respected even under speculation. Architectures which are affected by
72 speculation-based side-channels are expected to implement these
76 prevent information from being leaked via side-channels.
|
| /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
33 frameworks (where the same I/O model is used by both host and device
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,aoss-qmp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/qcom/qcom,aoss-qmp.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Always-On Subsystem side channel
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
13 This binding describes the hardware component responsible for side channel
14 requests to the always-on subsystem (AOSS), used for certain power management
15 requests that is not handled by the standard RPMh interface. Each client in the
20 The AOSS side channel exposes control over a set of resources, used to control
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | airoha,en8811h.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Eric Woudstra <ericwouds@gmail.com>
14 on the lines to and/or from the MAC. It is reversed by
18 - $ref: ethernet-phy.yaml#
23 - ethernet-phy-id03a2.a411
28 airoha,pnswap-rx:
32 side of the lines from the MAC towards the EN881H.
34 airoha,pnswap-tx:
[all …]
|
| /Documentation/networking/ |
| D | snmp_counter.rst | 10 these counters won't be changed by layer 2 packets (such as STP) or
17 .. _RFC1213 ipInReceives: https://tools.ietf.org/html/rfc1213#page-26
19 The number of packets received by the IP layer. It gets increasing at the
30 .. _RFC1213 ipInDelivers: https://tools.ietf.org/html/rfc1213#page-28
41 .. _RFC1213 ipOutRequests: https://tools.ietf.org/html/rfc1213#page-28
60 .. _Explicit Congestion Notification: https://tools.ietf.org/html/rfc3168#page-6
73 .. _RFC1213 ipInHdrErrors: https://tools.ietf.org/html/rfc1213#page-27
81 .. _RFC1213 ipInAddrErrors: https://tools.ietf.org/html/rfc1213#page-27
94 layer 4 protocol is unsupported by kernel. If an application is using
98 .. _RFC1213 ipInUnknownProtos: https://tools.ietf.org/html/rfc1213#page-27
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | fsl,mu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dong Aisheng <aisheng.dong@nxp.com>
14 communicate and coordinate by passing messages (e.g. data, status
19 different clocks (from each side of the different peripheral buses).
20 Therefore, the MU must synchronize the accesses from one side to the
22 registers (Processor A-facing, Processor B-facing).
27 - const: fsl,imx6sx-mu
28 - const: fsl,imx7ulp-mu
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-vntb-howto.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Non-Transparent Bridge (NTB) Endpoint Function (EPF) User Guide
9 This document is a guide to help users use pci-epf-vntb function driver
11 be followed in the host side and EP side is given below. For the hardware
13 Documentation/PCI/endpoint/pci-vntb-function.rst
19 ---------------------------
32 -------------------------
36 # ls /sys/bus/pci-epf/drivers
45 Creating pci-epf-vntb Device
46 ----------------------------
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rnbd-client | 1 What: /sys/class/rnbd-client
5 Description: Provide information about RNBD-client.
6 All sysfs files that are not read-only provide the usage information on read:
10 # cat /sys/class/rnbd-client/ctl/map_device
13 > [path=<[srcaddr,]dstaddr>] device_path=<full path on remote side>
18 What: /sys/class/rnbd-client/ctl/map_device
26 device_path=<full path on remote side>
34 I.e. "clt_hostname-srv_hostname" could be a natural choice.
37 describes a connection between the client and the server by
63 Path to the block device on the server side. Path is specified
[all …]
|
| D | sysfs-bus-surface_aggregator-tabletsw | 6 This attribute returns a string with the current type-cover
7 or device posture, as indicated by the embedded controller.
10 - "disconnected": The type-cover has been disconnected.
12 - "closed": The type-cover has been folded closed and lies on
15 - "laptop": The type-cover is open and in laptop-mode, i.e.,
18 - "folded-canvas": The type-cover has been folded back
19 part-ways, but does not lie flush with the back side of the
20 device. In general, this means that the kick-stand is used
23 - "folded-back": The type cover has been fully folded back and
24 lies flush with the back side of the device.
[all …]
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm
16 ---------
29 cluster-level operations are only performed when it is truly safe to do
35 disabling those mechanisms may itself be a non-atomic operation (such as
38 power-down and power-up at the cluster level.
46 -----------
50 - DOWN
51 - COMING_UP
52 - UP
53 - GOING_DOWN
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 24 character device ``/dev/tpmX`` (with X=0,1,2...) and a 'server side' file
25 descriptor. The former is moved into the container by creating a character
34 whether TPM 1.2 or TPM 2 functionality is supported by the TPM emulator.
35 The result of the ioctl are the file descriptor for the 'server side'
42 returned by the ioctl. The commands should be responded to immediately.
47 .. kernel-doc:: include/uapi/linux/vtpm_proxy.h
49 .. kernel-doc:: drivers/char/tpm/tpm_vtpm_proxy.c
|
| /Documentation/virt/ |
| D | guest-halt-polling.rst | 9 This provides the following benefits to host side polling:
15 2) The VM-exit cost can be avoided.
17 The downside of guest side polling is that polling is performed
21 is configured by the user, indicating the maximum amount of
25 ("per-cpu guest_halt_poll_ns"), which is adjusted by the algorithm
42 Division factor used to shrink per-cpu guest_halt_poll_ns when
49 Multiplication factor used to grow per-cpu guest_halt_poll_ns
50 when event occurs after per-cpu guest_halt_poll_ns
57 The per-cpu guest_halt_poll_ns eventually reaches zero
59 per-cpu guest_halt_poll_ns when growing. This can
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-input.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_INPUT - VIDIOC_S_INPUT - Query or select the current video input
30 File descriptor returned by :c:func:`open()`.
46 to this integer. Side effects are possible. For example inputs may
48 the current standard. Because of these possible side effects
58 On success 0 is returned, on error -1 and the ``errno`` variable is set
60 :ref:`Generic Error Codes <gen-errors>` chapter.
|
12345678910>>...16