| /openbmc/linux/Documentation/ |
| H A D | atomic_bitops.txt | 5 While our bitmap_{}() functions are non-atomic, we have a number of operations
12 The single bit operations are:
18 RMW atomic operations without return value:
23 RMW atomic operations with return value:
33 All RMW atomic operations have a '__' prefixed variant which is non-atomic.
47 The test_and_{}_bit() operations return the original value of the bit.
55 - non-RMW operations are unordered;
57 - RMW operations that have no return value are unordered;
59 - RMW operations that have a return value are fully ordered.
61 - RMW operations that are conditional are fully ordered.
[all …]
|
| H A D | atomic_t.txt | 5 RMW operations between CPUs (atomic operations on MMIO are not supported and
20 RMW atomic operations:
138 - plain operations without return value: atomic_{}()
146 - operations which return the original value: atomic_fetch_{}()
148 - swap operations: xchg(), cmpxchg() and try_cmpxchg()
155 All these operations are SMP atomic; that is, the operations (for a single
165 - non-RMW operations are unordered;
167 - RMW operations that have no return value are unordered;
169 - RMW operations that have a return value are fully ordered;
171 - RMW operations that are conditional are unordered on FAILURE,
[all …]
|
| /openbmc/u-boot/drivers/fpga/ |
| H A D | xilinx.c | 148 if (!desc->operations || !desc->operations->load) { in xilinx_load()
153 return desc->operations->load(desc, buf, bsize, bstype); in xilinx_load()
165 if (!desc->operations || !desc->operations->loadfs) { in xilinx_loadfs()
170 return desc->operations->loadfs(desc, buf, bsize, fpga_fsinfo); in xilinx_loadfs()
183 if (!desc->operations || !desc->operations->loads) { in xilinx_loads()
188 return desc->operations->loads(desc, buf, bsize, fpga_sec_info); in xilinx_loads()
199 if (!desc->operations || !desc->operations->dump) { in xilinx_dump()
204 return desc->operations->dump(desc, buf, bsize); in xilinx_dump()
276 if (desc->operations && desc->operations->info) in xilinx_info()
277 desc->operations->info(desc); in xilinx_info()
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 2 operations provided by the Linux-kernel memory model (LKMM).
9 operations in decreasing order of strength:
13 subsequent operations.
83 operations include value-returning RMW atomic operations (that is, those
247 a. Release operations.
249 b. Acquire operations.
292 There is a wide variety of release operations:
443 a. Unordered marked operations.
457 These operations come in three categories:
465 operations, unless these operations are to the same variable.
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | atomics.rst | 4 Atomic operations in QEMU
7 CPUs perform independent memory operations effectively in random order.
71 operations::
95 Similar operations return the new value of ``*ptr``::
129 components of the system, after all the LOAD or STORE operations
132 - release operations will *synchronize with* acquire operations;
145 before all the LOAD or STORE operations specified afterwards.
151 after all the LOAD or STORE operations specified before.
304 (for acquire) or after previous operations (for release).
356 as acquire operations. ``smp_wmb()``, ``smp_mb_release()``,
[all …]
|
| H A D | bitops.rst | 2 Bitwise operations
6 performing bitwise operations.
|
| /openbmc/linux/Documentation/virt/ |
| H A D | paravirt_ops.rst | 11 hypervisors. It allows each hypervisor to override critical operations and
15 pv_ops provides a set of function pointers which represent operations
18 time by enabling binary patching of the low-level critical operations
21 pv_ops operations are classified into three categories:
24 These operations correspond to high-level functionality where it is
28 Usually these operations correspond to low-level critical instructions. They
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | firmware.rst | 2 Interface for registering and calling firmware-specific operations for ARM
10 operations and call them when needed.
12 Firmware operations can be specified by filling in a struct firmware_ops
21 There is a default, empty set of operations provided, so there is no need to
22 set anything if platform does not require firmware operations.
33 Example of registering firmware operations::
52 /* other operations not available on platformX */
|
| /openbmc/linux/Documentation/bpf/standardization/ |
| H A D | instruction-set.rst | 220 otherwise identical operations.
292 Shift operations use a mask of 0x3F (63) for 64-bit operations and 0x1F (31)
293 for 32-bit operations.
344 otherwise identical operations.
435 BPF_MEMSX 0x80 sign-extension load operations `Sign-extension load operations`_
436 BPF_ATOMIC 0xc0 atomic operations `Atomic operations`_
471 Sign-extension load operations
484 Atomic operations
487 Atomic operations are operations that operate on memory and can not be
491 All atomic operations supported by BPF are encoded as store operations
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | this_cpu_ops.rst | 2 this_cpu operations
8 this_cpu operations are a way of optimizing access to per cpu
14 this_cpu operations add a per cpu variable offset to the processor
24 Read-modify-write operations are of particular interest. Frequently
39 (remote write operations) of local RMW operations via this_cpu_*.
42 operations.
45 are defined. These operations can be used without worrying about
64 Inner working of this_cpu operations
127 Special operations
166 cpu variable. Most this_cpu operations take a cpu variable.
[all …]
|
| H A D | local_ops.rst | 11 This document explains the purpose of the local atomic operations, how
18 Note that ``local_t`` based operations are not recommended for general
19 kernel use. Please use the ``this_cpu`` operations instead unless there is
21 replaced by ``this_cpu`` operations. ``this_cpu`` operations combine the
26 Purpose of local atomic operations
29 Local atomic operations are meant to provide fast and highly reentrant per CPU
30 counters. They minimize the performance cost of standard atomic operations by
39 Local atomic operations only guarantee variable modification atomicity wrt the
50 It can be done by slightly modifying the standard atomic operations: only
63 Rules to follow when using local atomic operations
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl_iim | 25 Fuse operations:
28 Read operations are implemented as read accesses to the shadow registers,
33 Sense operations are implemented as explained in 30.4.5.2.
36 Program operations are implemented as explained in 30.4.5.3. Following
42 Override operations are implemented as write accesses to the shadow
|
| H A D | README.mxc_ocotp | 28 Fuse operations:
31 Read operations are implemented as read accesses to the shadow registers,
36 Sense operations are implemented as the direct fusebox read explained by
40 Program operations are implemented as explained by the steps in 46.2.1.3.
45 Override operations are implemented as write accesses to the shadow
|
| /openbmc/webui-vue/tests/unit/__snapshots__/ |
| H A D | AppNavigation.spec.js.snap | 239 aria-controls="operations"
260 appNavigation.operations
291 id="operations"
309 href="#/operations/kvm"
327 href="#/operations/firmware"
354 href="#/operations/server-power-operations"
918 aria-controls="operations"
939 appNavigation.operations
970 id="operations"
988 href="#/operations/kvm"
[all …]
|
| /openbmc/phosphor-webui/app/server-control/styles/ |
| H A D | power-operations.scss | 3 .power-operations {
53 .boot-operations {
74 .operations-wrapper {
129 } //end power-operations
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | async-tx-api.rst | 15 3.2 Supported operations
36 the API will fit the chain of operations to the available offload
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
71 3.2 Supported operations
97 operations complete. When an application needs to submit a chain of
113 async_<operation> call. Offload engine drivers batch operations to
116 automatically issues pending operations. An application can force this
129 chains and issuing pending operations.
143 2. Completion callback routines cannot submit new operations. This
207 handle submission of dependent operations
[all …]
|
| /openbmc/linux/mm/damon/ |
| H A D | Kconfig | 28 bool "Data access monitoring operations for virtual address spaces"
32 This builds the default data access monitoring operations for DAMON
36 bool "Data access monitoring operations for the physical address space"
40 This builds the default data access monitoring operations for DAMON
44 bool "Test for DAMON operations" if !KUNIT_ALL_TESTS
48 This builds the DAMON virtual addresses operations Kunit test suite.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | nfc.rst | 21 responsible for providing an interface to control operations and low-level
24 The control operations are available to userspace via generic netlink.
36 | data exchange | operations
71 The userspace interface is divided in control operations and low-level data
76 Generic netlink is used to implement the interface to the control operations.
77 The operations are composed by commands and events, all listed below:
100 All polling operations requested through one netlink socket are stopped when
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/ |
| H A D | mv-xor.txt | 20 - dmacap,memcpy to indicate that the XOR channel is capable of memcpy operations
21 - dmacap,memset to indicate that the XOR channel is capable of memset operations
22 - dmacap,xor to indicate that the XOR channel is capable of xor operations
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-pfo-nx-crypto | 33 The total number of AES operations submitted to the hardware.
39 The total number of SHA-256 operations submitted to the hardware.
45 The total number of SHA-512 operations submitted to the hardware.
|
| /openbmc/linux/Documentation/arch/arm/vfp/ |
| H A D | release-notes.rst | 19 The operations which have been tested with this package are:
41 Other operations which have been tested by basic assembly-only tests
51 The combination operations have not been tested:
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | hisi-pmu.rst | 64 This will only count the operations from core/thread 0 and 1 in this cluster.
67 operations via the tt_req parameeter in perf. The default value counts all
68 operations. tt_req is 3bits, 3'b100 represents read operations, 3'b101
69 represents write operations, 3'b110 represents atomic store operations and
70 3'b111 represents atomic non-store operations, other values are reserved::
74 This will only count the read operations in this cluster.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | clk.rst | 17 gating, rate adjustment, muxing or other operations. This framework is
25 drivers/clk/clk.c. Finally there is struct clk_ops, whose operations
67 the operations defined in clk-provider.h::
175 To take advantage of your data you'll need to support valid operations
276 .disable operations. Those operations are thus not allowed to sleep,
290 The prepare lock is a mutex and is held across calls to all other operations.
291 All those operations are allowed to sleep, and calls to the corresponding API
294 This effectively divides operations in two groups from a locking perspective.
296 Drivers don't need to manually protect resources shared between the operations
304 framework functions from within its implementation of clock operations. This
[all …]
|
| /openbmc/linux/Documentation/netlink/specs/ |
| H A D | devlink.yaml | 251 operations:
307 # TODO: fill in the operations in between
333 # TODO: fill in the operations in between
360 # TODO: fill in the operations in between
388 # TODO: fill in the operations in between
417 # TODO: fill in the operations in between
443 # TODO: fill in the operations in between
470 # TODO: fill in the operations in between
522 # TODO: fill in the operations in between
548 # TODO: fill in the operations in between
[all …]
|
| /openbmc/linux/Documentation/filesystems/spufs/ |
| H A D | spufs.rst | 45 the operations supported on regular file systems. This list details the
46 supported operations and the deviations from the behaviour in the
51 All files support the access(2) and stat(2) family of operations, but
57 possible operations, e.g. read access on the wbox file.
65 data in the address space of the SPU. The possible operations on an
84 operations on an open mbox file are:
98 operations on an open ibox file are:
121 operations on an open wbox file are: write(2) If a count smaller than
143 operations on an open ``*box_stat`` file are:
173 The possible operations on an open npc, decr, decr_status,
[all …]
|