| /openbmc/pldm/libpldmresponder/test/ |
| H A D | libpldmresponder_bios_enum_attribute_test.cpp | 39 "possible_values" : [ "Concurrent", "Disruptive" ], in TEST_F()
40 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
41 "default_values" : [ "Concurrent" ], in TEST_F()
51 ElementsAreArray({"Concurrent", "Disruptive"})); in TEST_F()
52 EXPECT_EQ(getDefaultValue(enumReadOnly), "Concurrent"); in TEST_F()
56 "possible_value" : [ "Concurrent", "Disruptive" ], in TEST_F()
57 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
58 "default_values" : [ "Concurrent" ], in TEST_F()
96 "possible_values" : [ "Concurrent", "Disruptive" ], in TEST_F()
97 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | kcsan-checks.h | 340 * ASSERT_EXCLUSIVE_WRITER - assert no concurrent writes to @var
342 * Assert that there are no concurrent writes to @var; other readers are
343 * allowed. This assertion can be used to specify properties of concurrent code,
346 * For example, if we only have a single writer, but multiple concurrent
348 * concurrent marked writes racing with the single writer are bugs.
366 * checking if a clear scope where no concurrent writes are expected exists.
388 * ASSERT_EXCLUSIVE_WRITER_SCOPED - assert no concurrent writes to @var in scope
392 * Assert that there are no concurrent writes to @var for the duration of the
423 * ASSERT_EXCLUSIVE_ACCESS - assert no concurrent accesses to @var
425 * Assert that there are no concurrent accesses to @var (no readers nor
[all …]
|
| H A D | kfifo.h | 220 * from the reader thread and there is only one concurrent reader. Otherwise
402 * Note that with only one concurrent reader and one concurrent
439 * Note that with only one concurrent reader and one concurrent
478 * Note that with only one concurrent reader and one concurrent
516 * Note that with only one concurrent reader and one concurrent
584 * Note that with only one concurrent reader and one concurrent
659 * Note that with only one concurrent reader and one concurrent
687 * Note that with only one concurrent reader and one concurrent
715 * Note that with only one concurrent reader and one concurrent
739 * Note that with only one concurrent reader and one concurrent
[all …]
|
| H A D | rcuref.h | 107 * the last reference and the slowpath races against a concurrent get() and
116 * with a concurrent get()/put() pair. Caller is not allowed to
142 * with a concurrent get()/put() pair. Caller is not allowed to
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 4 This document provides guidelines for marking intentionally concurrent
183 5. Any other loads for which there is not supposed to be a concurrent
186 6. Any other stores for which there should be neither concurrent
187 loads nor concurrent stores to that same variable.
221 concurrent access to variable foo by any other CPU is an error, even
222 if that concurrent access is marked with READ_ONCE(). In addition,
224 to be concurrent reads from foo from other CPUs, it is an error for some
225 other CPU to be concurrently writing to foo, even if that concurrent
238 your concurrent algorithm, to help the human reader, and to inform
345 concurrent lockless write.
[all …]
|
| H A D | ordering.txt | 273 different pieces of the concurrent algorithm. The variable stored to
275 an acquire operation in other parts of the concurrent algorithm.
331 the different pieces of the concurrent algorithm by looking for the
481 concurrent atomic_inc() operations applied to a given variable
509 concurrent code. It is possible to used unmarked C-language accesses for
510 shared variables that are subject to concurrent access, but great care
524 so that there are never concurrent conflicting accesses to
526 (1) at least one of the concurrent accesses to a variable is an
533 o Use locking or other means to ensure that all concurrent accesses
|
| /openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
| H A D | test_vmicert_management.robot | 149 Get Concurrent Root Certificate Requests From Multiple Admin Users
150 [Documentation] Get multiple concurrent root certificate requests from multiple admins
164 Get Concurrent CSR Requests From Multiple Admin Users
165 [Documentation] Get multiple concurrent csr requests from multiple admins and verify no errors.
179 Get Concurrent Corrupted CSR Requests From Multiple Admin Users
180 …[Documentation] Get multiple concurrent corrupted csr requests from multiple admins and verify no…
195 Get Concurrent Root Certificate Request From Operator Users
196 …[Documentation] Get multiple concurrent root certificate from non admin users and verify no error…
211 Get Concurrent Root Certificate Request From Admin And Non Admin Users
212 [Documentation] Get multiple concurrent root certificate from admin and non admin users
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | lockcnt.rst | 66 protect readers from other threads freeing memory after concurrent
133 Note that it is possible for multiple concurrent accesses to delay
136 more easily applicable if concurrent access to the structure is rare.
149 :doc:`atomics`). This can be very helpful if concurrent access to
160 - concurrent access is possible but rare
171 concurrent with a visit to the list of bottom halves; 2) it only has
210 is zero (i.e. there is no concurrent visit). Because ``qemu_lockcnt_inc``
|
| /openbmc/linux/drivers/net/ethernet/microchip/ |
| H A D | lan743x_ptp.h | 29 /* gpio_lock: used to prevent concurrent access to gpio settings */
74 /* command_lock: used to prevent concurrent ptp commands */
89 /* tx_ts_lock: used to prevent concurrent access to timestamp arrays */
|
| /openbmc/obmc-console/ |
| H A D | meson.options | 2 option('concurrent-servers', type: 'boolean', value: false, description: 'Support multiple concurre…
|
| /openbmc/pldm/libpldmresponder/examples/bios/ |
| H A D | enum_attrs.json | 49 "possible_values": ["Concurrent", "Disruptive"],
50 "default_values": ["Concurrent"]
|
| /openbmc/linux/drivers/usb/gadget/function/ |
| H A D | g_zero.h | 43 * This is to protect the data from concurrent access by read/write
58 * This is to protect the data from concurrent access by read/write
|
| /openbmc/linux/lib/ |
| H A D | rcuref.c | 28 * O(N^2) behaviour under contention with N concurrent operations.
65 * concurrent rcuref_get() can acquire the reference count and bring it
68 * If the cmpxchg() succeeds then a concurrent rcuref_get() will result in
233 * with a concurrent get()/put() pair. Caller is not allowed to
245 * This can fail if a concurrent get() operation has in rcuref_put_slowpath()
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/console/ |
| H A D | obmc-console_git.bb | 14 PACKAGECONFIG[concurrent-servers] = "-Dconcurrent-servers=true,-Dconcurrent-servers=false,"
30 # `concurrent-servers` in PACKAGECONFIG.
33 SYSTEMD_SERVICE:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'concurrent-servers', '', '${SSH_SY…
|
| /openbmc/linux/drivers/clk/sifive/ |
| H A D | sifive-prci.c | 309 * Context: Any context. Caller must prevent concurrent changes to the
330 * Context: Any context. Caller must prevent concurrent changes to the
352 * Context: Any context. Caller must prevent concurrent changes to the
373 * Context: Any context. Caller must prevent concurrent changes to the
394 * Context: Any context. Caller must prevent concurrent changes to the
415 * Context: Any context. Caller must prevent concurrent changes to the
436 * Context: Any context. Caller must prevent concurrent changes to the
|
| /openbmc/qemu/util/ |
| H A D | qemu-coroutine-lock.c | 119 * lock-free queue. There cannot be two concurrent pop_waiter() calls
132 * a concurrent qemu_co_mutex_lock will fail the cmpxchg, and
211 * a concurrent unlock() the responsibility of waking somebody up. in qemu_co_mutex_lock_slowpath()
217 /* There can be no concurrent pops, because there can be only in qemu_co_mutex_lock_slowpath()
303 /* Some concurrent lock() is in progress (we know this because in qemu_co_mutex_unlock()
315 /* The concurrent lock has not added itself yet, so it in qemu_co_mutex_unlock()
|
| /openbmc/qemu/docs/spin/ |
| H A D | tcg-exclusive.promela | 36 # warning defaulting to 2 concurrent exclusive sections
39 # warning defaulting to 1 concurrent exclusive sections
136 // Wait-free fast path, only needs mutex when concurrent with
|
| /openbmc/linux/tools/include/uapi/asm-generic/ |
| H A D | fcntl.h | 188 #define LOCK_READ 64 /* which allows concurrent read operations */
189 #define LOCK_WRITE 128 /* which allows concurrent write operations */
190 #define LOCK_RW 192 /* which allows concurrent read & write ops */
|
| /openbmc/linux/include/uapi/asm-generic/ |
| H A D | fcntl.h | 188 #define LOCK_READ 64 /* which allows concurrent read operations */
189 #define LOCK_WRITE 128 /* which allows concurrent write operations */
190 #define LOCK_RW 192 /* which allows concurrent read & write ops */
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | gdbserver.py | 10 import concurrent.futures
49 with concurrent.futures.ThreadPoolExecutor(max_workers=1) as executor:
|
| /openbmc/linux/arch/arc/mm/ |
| H A D | highmem.c | 26 * means the total number of concurrent fixmaps will be limited to max
42 * - pkmap being preemptible, in theory could do with more than 256 concurrent
|
| /openbmc/linux/fs/xfs/ |
| H A D | xfs_aops.c | 217 * because concurrent changes could have invalidated the extent. Check in xfs_imap_valid()
218 * the COW fork because concurrent changes since the last time we in xfs_imap_valid()
268 * we've indirectly protected against concurrent updates: writeback has in xfs_map_blocks()
269 * the page locked, which prevents concurrent invalidations by reflink in xfs_map_blocks()
270 * and directio and prevents concurrent buffered writes to the same in xfs_map_blocks()
272 * against concurrent updates and provides a memory barrier on the way in xfs_map_blocks()
|
| /openbmc/pldm/libpldmresponder/test/system_type1/bios_jsons/ |
| H A D | bios_attrs.json | 57 "possible_values": ["Concurrent", "Disruptive"],
58 "default_values": ["Concurrent"],
|
| /openbmc/pldm/libpldmresponder/test/bios_jsons/ |
| H A D | bios_attrs.json | 57 "possible_values": ["Concurrent", "Disruptive"],
58 "default_values": ["Concurrent"],
|
| /openbmc/linux/security/landlock/ |
| H A D | object.h | 34 * in a safe way. This implies to handle concurrent use and modification.
50 * @lock: Protects against concurrent modifications. This lock must be
|