| /openbmc/linux/tools/perf/pmu-events/arch/x86/silvermont/ |
| H A D | virtual-memory.json | 12 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)",
20 "BriefDescription": "Duration of D-side page-walks in core cycles",
23 …when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number…
28 "BriefDescription": "D-side page-walks",
32 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number …
37 "BriefDescription": "Duration of I-side page-walks in core cycles",
40 …I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by…
45 "BriefDescription": "I-side page-walks",
49 …ce a page walk implies a TLB miss, the number of TLB misses can be counted by counting the number …
54 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
[all …]
|
| /openbmc/linux/Documentation/locking/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/RCU/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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 …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | rcu.rst | 1 Using RCU (Read-Copy-Update) for synchronization
4 Read-copy update (RCU) is a synchronization mechanism that is used to
5 protect read-mostly data structures. RCU is very efficient and scalable
6 on the read side (it is wait-free), and thus can make the read paths
10 thus it is not used alone. Typically, the write-side will use a lock to
17 RCU is fundamentally a "wait-to-finish" mechanism. The read side marks
18 sections of code with "critical sections", and the update side will wait
26 for example, reader-writer locks. It is so much more scalable that
43 ------------------- ------------------------ -------------------
61 -------
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/ampere/ampereone/ |
| H A D | core-imp-def.json | 99 "PublicDescription": "Macro-ops speculatively decoded",
102 "BriefDescription": "Macro-ops speculatively decoded"
249 "PublicDescription": "Number of SWOB drains triggered by timeout",
252 "BriefDescription": "Number of SWOB drains triggered by timeout"
255 … "Number of SWOB drains triggered by system register or special-purpose register read-after-write …
258 … "Number of SWOB drains triggered by system register or special-purpose register read-after-write …
261 … "PublicDescription": "Number of SWOB drains triggered by system register write when SWOB full",
264 … "BriefDescription": "Number of SWOB drains triggered by system register write when SWOB full"
297 "PublicDescription": "Instructions issued by the scheduler",
300 "BriefDescription": "Instructions issued by the scheduler"
[all …]
|
| /openbmc/linux/Documentation/usb/ |
| H A 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 …]
|
| /openbmc/linux/drivers/block/rnbd/ |
| H A D | README | 6 ------------
12 on the client side as local block devices.
14 I/O is transferred between client and server by the RTRS transport
19 ------------
24 -----------
26 Server side:
29 Client side:
32 /sys/devices/virtual/rnbd-client/ctl/map_device
36 a pair of a source and a destination IPs, separated by comma. Multiple
39 mapped from the server side. After the session to the server machine is
[all …]
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A 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 …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 4 While I2C supports multi-master buses this is difficult to get right.
5 The implementation on the master side in software is quite complex.
6 Clock-stretching and the arbitrary time that an I2C transaction can take
8 When one or more masters can be reset independently part-way through a
11 U-Boot provides a scheme based on two 'claim' GPIOs, one driven by the
12 AP (Application Processor, meaning the main CPU) and one driven by the EC
16 reboots by either side without difficulty.
18 Since U-Boot runs on the AP, the terminology used is 'our' claim GPIO,
20 is used by the device tree bindings in Linux also.
23 i2c-arb-gpio-challenge for the implementation.
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-cache.json | 13 …ted information by filtering the Cb0 occupancy count captured in Counter 0. The filtering availa…
21 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
30 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
39 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa…
48 … LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numer…
57 …- this includes code, data, prefetches and hints coming from L2. This has numerous filters availa…
66 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
75 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
84 … the number of lines that were victimized on a fill. This can be filtered by the state that the l…
93 …imized on a fill. This can be filtered by the state that the line was in.; Qualify one of the oth…
[all …]
|
| /openbmc/pldm/oem/ibm/libpldmresponder/ |
| H A D | inband_code_update.hpp | 27 * notification to phosphor-software-manager app
33 * @param[in] dBusIntf - D-Bus handler pointer
44 /* @brief Method to return the current boot side
48 /* @brief Method to return the next boot side
52 /* @brief Method to set the current boot side or
53 * perform a rename operation on current boot side
54 * @param[in] currSide - current side to be set to
59 /* @brief Method to set the next boot side
60 * @param[in] nextSide - next boot side to be set to
65 /* @brief Method to set the running and non-running
[all …]
|
| /openbmc/linux/drivers/char/ipmi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate 'IPMI top-level message handler'
17 See <file:Documentation/driver-api/ipmi.rst> for more details on the driver.
34 by default, generate an IPMI event describing the panic to each
45 by default, generate IPMI OEM type f0 events holding the IPMB
91 Provides a driver for OPAL firmware-based IPMI interfaces.
118 The driver implements the BMC side of the KCS contorller, it
119 provides the access of KCS IO space for BMC side.
130 The driver implements the BMC side of the KCS contorller, it
131 provides the access of KCS IO space for BMC side.
[all …]
|
| /openbmc/linux/drivers/char/hw_random/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
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
31 the default FPGA bitstream on the TS-7800 has such functionality.
34 module will be called timeriomem-rng.
43 This driver provides kernel-side support for the Random Number
44 Generator hardware found on Intel i8xx-based motherboards.
47 module will be called intel-rng.
57 This driver provides kernel-side support for the Random Number
[all …]
|
| /openbmc/openbmc-test-automation/pldm/ |
| H A D | test_firmware_boot_side.robot | 3 Documentation Test firmware boot side switch using pldmtool.
7 # 2. Check the firmware boot side ( login to BMC and execute )
9 # pldmtool bios GetBIOSAttributeCurrentValueByHandle -a fw_boot_side
12 # 3. Set the firmware boot side to Temp or Perm accordingly
14 # pldmtool bios SetBIOSAttributeCurrentValue -a fw_boot_side -d Temp
19 # 7. Verify the boot side is still same which was set.
33 # By default 2, to ensure, it performs both Perm and Temp side switch and boot.
36 # This dictionary is for Temp -> Perm or vice versa in the test code.
41 Test Firmware Boot Side Using Pldmtool
42 [Documentation] Power off the host , set the firmware boot side via pldmtool,
[all …]
|
| /openbmc/linux/drivers/media/platform/mediatek/vcodec/encoder/venc/ |
| H A D | venc_h264_if.c | 1 // SPDX-License-Identifier: GPL-2.0
27 * enum venc_h264_frame_type - h264 encoder output bitstream frame type
37 * enum venc_h264_vpu_work_buf - h264 encoder buffer index
53 * enum venc_h264_bs_mode - for bs_mode argument in h264_enc_vpu_encode
62 * struct venc_h264_vpu_config - Structure for h264 encoder configuration
63 * AP-W/R : AP is writer/reader on this item
64 * VPU-W/R: VPU is write/reader on this item
97 * struct venc_h264_vpu_buf - Structure for buffer information
98 * AP-W/R : AP is writer/reader on this item
99 * VPU-W/R: VPU is write/reader on this item
[all …]
|
| H A D | venc_vp8_if.c | 1 // SPDX-License-Identifier: GPL-2.0
27 * enum venc_vp8_vpu_work_buf - vp8 encoder buffer index
47 * struct venc_vp8_vpu_config - Structure for vp8 encoder configuration
48 * AP-W/R : AP is writer/reader on this item
49 * VPU-W/R: VPU is write/reader on this item
62 * support three temporal layers - 0: 7.5fps 1: 7.5fps 2: 15fps.
77 * struct venc_vp8_vpu_buf - Structure for buffer information
78 * AP-W/R : AP is writer/reader on this item
79 * VPU-W/R: VPU is write/reader on this item
81 * @vpua: VPU side memory addr which is used by RC_CODE
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | uncore-interconnect.json | 41 …": "Coherent Ops : CLFlush : Counts the number of coherency related operations servied by the IRP",
46 …"BriefDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of writ…
50 …"PublicDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of wri…
55 …"BriefDescription": "RFO request issued by the IRP unit to the mesh with the intention of writing …
59 …"PublicDescription": "RFO request issued by the IRP unit to the mesh with the intention of writing…
68 …n": "Coherent Ops : WbMtoI : Counts the number of coherency related operations servied by the IRP",
80 … "BriefDescription": "Inbound read requests received by the IRP and inserted into the FAF queue.",
84 …"PublicDescription": "Inbound read requests to coherent memory, received by the IRP and inserted i…
96 "BriefDescription": "FAF allocation -- sent to ADQ",
127 … "BriefDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary",
[all …]
|
| /openbmc/linux/include/linux/ |
| H A 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 -
83 * srcu_read_lock_held - might we be in SRCU read-side critical section?
87 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
88 * this assumes we are in an SRCU read-side critical section unless it can
102 return lock_is_held(&ssp->dep_map); in srcu_read_lock_held()
109 * srcu_lock_sync(), which is basically an empty *write*-side critical section,
157 * srcu_dereference_check - fetch SRCU-protected pointer for later dereferencing
160 * really are in an SRCU read-side critical section.
[all …]
|
| H A D | rcupdate.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Read-Copy Update mechanism for mutual exclusion
9 * Based on the original work by Paul McKenney <paulmck@vnet.ibm.com>
15 * For detailed explanation of Read-Copy Update mechanism see -
35 #define ULONG_CMP_GE(a, b) (ULONG_MAX / 2 >= (a) - (b))
36 #define ULONG_CMP_LT(a, b) (ULONG_MAX / 2 < (a) - (b))
38 #define USHORT_CMP_GE(a, b) (USHRT_MAX / 2 >= (unsigned short)((a) - (b)))
39 #define USHORT_CMP_LT(a, b) (USHRT_MAX / 2 < (unsigned short)((a) - (b)))
52 // not-yet-completed RCU grace periods.
56 * same_state_synchronize_rcu - Are two old-state values identical?
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/powerpc/power9/ |
| H A D | translation.json | 20 "BriefDescription": "Double-Precion or Quad-Precision instruction completed"
25 …m another chip's memory on the same Node or Group (Distant) due to a data side request. When using…
35 …chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a instruction side request"
60 … or L3 on a different Node or Group (Distant), as this chip due to a data side request. When using…
75 …ared or modified data from another core's L2/L3 on the same chip due to a instruction side request"
100 …e TLB from another chip's L4 on the same Node or Group ( Remote) due to a instruction side request"
115 …tions in 32 and 64 bit binary floating point format. Not qualified multicycle. Qualified by vector"
130 "BriefDescription": "Demand LD - L2 Miss (not L2 hit)"
140 …"BriefDescription": "The number a times the core transitioned from a stall to ICT-empty for this t…
145 …from a memory location including L4 from local remote or distant due to a instruction side request"
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A 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 …]
|
| /openbmc/linux/tools/testing/selftests/bpf/progs/ |
| H A D | cgroup_tcp_skb.c | 1 // SPDX-License-Identifier: GPL-2.0
29 if (skb->protocol != bpf_htons(ETH_P_IPV6)) in needed_tcp_pkt()
40 if (tcph->source != bpf_htons(g_sock_port) && in needed_tcp_pkt()
41 tcph->dest != bpf_htons(g_sock_port)) in needed_tcp_pkt()
51 if (tcph->fin || !tcph->syn || !tcph->ack) in egress_accept()
65 if (!tcph->syn || tcph->fin || tcph->ack) in ingress_accept()
71 if (tcph->fin || tcph->syn || !tcph->ack) in ingress_accept()
87 if (!tcph->syn || tcph->fin || tcph->ack) in egress_connect()
100 if (tcph->fin || !tcph->syn || !tcph->ack) in ingress_connect()
110 /* The connection is closed by the peer outside the cgroup. */
[all …]
|