| /openbmc/obmc-console/ |
| H A D | meson.options | 2 option('concurrent-servers', type: 'boolean', value: false, description: 'Support multiple concurre…
|
| /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/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,
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.
466 there really can be concurrent lockless writers. KCSAN would
[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/qemu/docs/devel/ |
| H A D | lockcnt.txt | 66 protect readers from other threads freeing memory after concurrent
132 Note that it is possible for multiple concurrent accesses to delay
135 more easily applicable if concurrent access to the structure is rare.
148 docs/devel/atomics.rst). This can be very helpful if concurrent access to
159 - concurrent access is possible but rare
170 concurrent with a visit to the list of bottom halves; 2) it only has
209 is zero (i.e. there is no concurrent visit). Because qemu_lockcnt_inc
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/console/ |
| H A D | obmc-console_git.bb | 14 PACKAGECONFIG[concurrent-servers] = "-Dconcurrent-servers=true,-Dconcurrent-servers=false,"
29 # `concurrent-servers` in PACKAGECONFIG.
32 SYSTEMD_SERVICE:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'concurrent-servers', '', '${SSH_SY…
|
| /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/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-greenlet_3.0.3.bb | 1 SUMMARY = "Python lightweight in-process concurrent programming"
|
| H A D | python3-eventlet_0.36.1.bb | 1 DESCRIPTION = "Highly concurrent networking library"
|
| H A D | python3-requests-futures_1.0.1.bb | 1 SUMMARY = "Small add-on for the python requests http library. Makes use of python 3.2’s concurrent.…
|
| /openbmc/openbmc/meta-ampere/meta-common/recipes-phosphor/console/ |
| H A D | obmc-console_%.bbappend | 12 PACKAGECONFIG:append = " concurrent-servers"
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/console/ |
| H A D | obmc-console_%.bbappend | 42 PACKAGECONFIG:append:p10bmc = " concurrent-servers"
60 EXTRA_OECONF:append:witherspoon-tacoma = " --enable-concurrent-servers"
|
| /openbmc/qemu/scripts/ci/gitlab-kubernetes-runners/ |
| H A D | values.yaml | 5 concurrent: 200
|
| /openbmc/linux/drivers/net/wireless/mediatek/mt76/mt7996/ |
| H A D | Kconfig | 11 which support concurrent tri-band operation at 6GHz, 5GHz,
|
| /openbmc/openbmc/meta-amd/meta-common/recipes-phosphor/console/ |
| H A D | obmc-console_%.bbappend | 23 EXTRA_OECONF:append = " --enable-concurrent-servers"
|
| /openbmc/linux/drivers/net/wireless/mediatek/mt76/mt7915/ |
| H A D | Kconfig | 11 which support concurrent dual-band operation at both 5GHz
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/concurrencykit/ |
| H A D | concurrencykit_git.bb | 4 concurrent systems."
|
| /openbmc/linux/tools/testing/kunit/ |
| H A D | run_checks.py | 10 from concurrent import futures
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/ace/ |
| H A D | ace_6.5.19.bb | 3 patterns for concurrent communication software"
|
| /openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
| H A D | test_vmicert_management.robot | 150 [Documentation] Get multiple concurrent root certificate requests from multiple admins
165 [Documentation] Get multiple concurrent csr requests from multiple admins and verify no errors.
180 …[Documentation] Get multiple concurrent corrupted csr requests from multiple admins and verify no…
196 …[Documentation] Get multiple concurrent root certificate from non admin users and verify no error…
212 [Documentation] Get multiple concurrent root certificate from admin and non admin users
228 [Documentation] Get multiple concurrent root certificate from different non admin users
243 [Documentation] Get multiple concurrent csr request from non admin users and verify no errors.
273 [Documentation] Get concurrent root certificate and send csr request
321 [Documentation] Send concurrent csr request and corrupted csr request
353 [Documentation] Send concurrent csr requests from admin and non-admin users and verify
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/VPD/ |
| H A D | Manager.interface.yaml | 111 to collect VPD of any given FRU in case of concurrent maintenance.
124 of concurrent maintenance. As a pre-requisite for this api,
|
| /openbmc/linux/drivers/net/wireless/mediatek/mt76/mt7615/ |
| H A D | Kconfig | 15 which support concurrent dual-band operation at both 5GHz
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/jemalloc/ |
| H A D | jemalloc_5.3.0.bb | 4 SUMMARY = "General-purpose scalable concurrent malloc implementation"
|
| /openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
| H A D | drbd-connection-state-overview.dot | 48 …cluster_resync [ shape=record,label="{<any>resynchronisation process running\l'concurrent' applica…
|
| /openbmc/pldm/tools/visualize-pdr/ |
| H A D | README.md | 5 Host FRU pdrs coming in due to concurrent maintenance of the system,where the
|