/openbmc/linux/Documentation/litmus-tests/atomic/ |
H A D | Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus | 1 C Atomic-RMW+mb__after_atomic-is-stronger-than-acquire 7 * stronger than a normal acquire: both the read and write parts of
|
/openbmc/linux/Documentation/litmus-tests/ |
H A D | README | 15 Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus 17 stronger than a normal acquire: both the read and write parts of
|
/openbmc/linux/Documentation/ |
H A D | atomic_t.txt | 225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than 234 strictly stronger than ACQUIRE. As illustrated: 236 C Atomic-RMW+mb__after_atomic-is-stronger-than-acquire
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-nice-design.rst | 17 much stronger than they were before in 2.4 (and people were happy about 111 automatically: stronger negative nice levels are an automatic
|
H A D | sched-design-CFS.rst | 108 The CFS scheduler has a much stronger handling of nice levels and SCHED_BATCH
|
/openbmc/linux/Documentation/devicetree/bindings/mtd/ |
H A D | fsmc-nand.txt | 37 Can support 1-bit HW ECC (default) or if stronger correction is required,
|
/openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/ |
H A D | fix-security-format.patch | 33 if (!error_in_archive) /* don't overwrite stronger error */
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | recipes.txt | 45 use READ_ONCE() and WRITE_ONCE() or stronger to prevent load/store 68 stronger than "Any CPU holding a given lock sees all changes made by any 344 Of course, given that smp_mb() is strictly stronger than either smp_wmb() 434 The ordering in this example is stronger than it needs to be. For
|
H A D | locking.txt | 21 Note that this statement is a bit stronger than "Any CPU holding a
|
H A D | ordering.txt | 415 A control dependency extends from a marked load (READ_ONCE() or stronger) 416 through an "if" condition to a marked store (WRITE_ONCE() or stronger)
|
/openbmc/linux/Documentation/process/ |
H A D | kernel-enforcement-statement.rst | 50 be stronger.
|
H A D | 1.Intro.rst | 168 are heard, but active developers have a stronger voice - and the ability
|
/openbmc/linux/Documentation/driver-api/early-userspace/ |
H A D | buffer-format.rst | 84 significantly stronger integrity check), however, this is the
|
/openbmc/qemu/docs/system/ |
H A D | cpu-models-x86.rst.inc | 140 Required to enable stronger Spectre v2 (CVE-2017-5715) fixes in some 276 Required to enable stronger Spectre v2 (CVE-2017-5715) fixes in some
|
/openbmc/docs/designs/ |
H A D | redfish-resource-supplement-for-pfr.md | 29 and component/device suppliers, to build stronger security mechanisms into
|
/openbmc/linux/fs/smb/client/ |
H A D | Kconfig | 76 man-in-the-middle attacks and stronger crypto hashes, so the use
|
/openbmc/qemu/docs/devel/ |
H A D | atomics.rst | 54 case, ``qemu/atomic.h`` will reduce stronger memory barriers to simple 194 stronger than both a read and a write memory barrier; it implies both
|
H A D | multi-thread-tcg.rst | 294 - host systems with stronger implied guarantees can skip some barriers
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | faq.rst | 154 usually TV cards need stronger signals than TV sets, and are more
|
/openbmc/linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
H A D | rs.c | 1851 int *weaker, int *stronger) in rs_get_adjacent_txp() argument 1857 *stronger = index - IWL_MVM_RS_TPC_TX_POWER_STEP; in rs_get_adjacent_txp() 1858 if (*stronger < 0) in rs_get_adjacent_txp() 1859 *stronger = TPC_INVALID; in rs_get_adjacent_txp()
|
/openbmc/docs/architecture/code-update/ |
H A D | emmc-storage-design.md | 117 and data in the filesystem, and therefore provides stronger guarantees on the
|
/openbmc/linux/Documentation/mm/ |
H A D | multigen_lru.rst | 58 The protection of the former channel is by design stronger because:
|
/openbmc/linux/Documentation/networking/dsa/ |
H A D | configuration.rst | 349 Since kernel v5.14, DSA has gained stronger integration with the bridge's
|
/openbmc/linux/Documentation/driver-api/ |
H A D | device-io.rst | 295 memory (e.g. I/O registers). Other modes can offer weaker or stronger
|
/openbmc/linux/Documentation/bpf/ |
H A D | kfuncs.rst | 411 significant value provide stronger incentives for maintainers to invest the
|