Searched full:coherence (Results 1 – 25 of 82) sorted by relevance
1234
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | glossary.txt | 42 Coherence (co): When one CPU's store to a given variable overwrites
44 there is said to be a coherence link from the second CPU to
47 It is also possible to have a coherence link within a CPU, which
48 is a "coherence internal" (coi) link. The term "coherence
115 See also "Coherence" and "Reads-from".
149 coherence and from-reads links.
156 See also Coherence" and "From-reads".
|
| D | explanation.txt | 19 11. CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe
608 CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe
611 Cache coherence is a general principle requiring that in a
615 ordering which all the CPUs agree on (the coherence order), and this
619 To put it another way, for any variable x, the coherence order (co) of
622 comes first in the coherence order; the store which directly
626 You can think of the coherence order as being the order in which the
630 coherence order, that is, if the value stored by W gets overwritten,
633 Coherence order is required to be consistent with program order. This
636 Write-write coherence: If W ->po-loc W' (i.e., W comes before
[all …]
|
| /linux-6.12.1/arch/mips/kernel/ |
| D | pm-cps.c | 387 * because they're needed in both the enable & disable coherence steps in cps_gen_entry_code()
406 * If this is the last VPE to become ready for non-coherence in cps_gen_entry_code()
415 * for non-coherence. It needs to wait until coherence in cps_gen_entry_code()
456 * disable coherence. At this point we *must* be sure that no other in cps_gen_entry_code()
483 /* Barrier to ensure write to coherence control is complete */ in cps_gen_entry_code()
488 /* Disable coherence */ in cps_gen_entry_code()
546 * VPEs which did not disable coherence will continue in cps_gen_entry_code()
547 * executing, after coherence has been disabled, from this in cps_gen_entry_code()
557 * Re-enable coherence. Note that for CPS_PM_NC_WAIT all coupled VPEs in cps_gen_entry_code()
558 * will run this. The first will actually re-enable coherence & the in cps_gen_entry_code()
[all …]
|
| /linux-6.12.1/arch/mips/include/asm/ |
| D | mips-cm.h | 27 * This function returns the physical base address of the Coherence Manager
28 * global control block, or 0 if no Coherence Manager is present. It provides
39 * This function returns the physical base address of the Coherence Manager
72 * mips_cm_probe - probe for a Coherence Manager
74 * Attempt to detect the presence of a Coherence Manager. Returns 0 if a CM
87 * mips_cm_present - determine whether a Coherence Manager is present
163 /* GCR_REV - Indicates the Coherence Manager revision */
302 /* GCR_Cx_COHERENCE - Controls core coherence */
303 GCR_CX_ACCESSOR_RW(32, 0x008, coherence)
|
| D | pm-cps.h | 11 * The CM & CPC can only handle coherence & power control on a per-core basis,
|
| D | mips-cps.h | 162 * zero if no Coherence Manager is present.
179 * if no Coherence Manager is present.
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-firmware-sgi_uv | 35 The coherence_id entry contains the coherence id.
36 A partitioned UV system can have one or more coherence
37 domains. The coherence id indicates which coherence domain
|
| /linux-6.12.1/tools/memory-model/litmus-tests/ |
| D | README | 6 Test of read-read coherence, that is, whether or not two
10 Test of read-write coherence, that is, whether or not a read
15 Test of write-read coherence, that is, whether or not a write
20 Test of write-write coherence, that is, whether or not two
|
| D | CoWW+poonceonce.litmus | 6 * Test of write-write coherence, that is, whether or not two successive
|
| D | CoRR+poonceonce+Once.litmus | 6 * Test of read-read coherence, that is, whether or not two successive
|
| D | CoRW+poonceonce+Once.litmus | 6 * Test of read-write coherence, that is, whether or not a read from
|
| D | CoWR+poonceonce+Once.litmus | 6 * Test of write-read coherence, that is, whether or not a write to a
|
| D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 10 * is a write-to-write link (AKA a "coherence" or just "co" link) and P2()
|
| /linux-6.12.1/arch/arm64/include/asm/ |
| D | cache.h | 97 * instruction to data coherence.
101 * 1 - dcache clean to PoU is not required for i-to-d coherence.
|
| /linux-6.12.1/tools/memory-model/ |
| D | linux-kernel.cat | 65 (* Fundamental coherence ordering *)
70 acyclic po-loc | com as coherence
204 (* Coherence requirements for plain accesses *)
208 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
|
| D | README | 183 satisfy the model's "coherence", "atomic", "happens-before",
217 for generation of the possible reads-from and coherence order
|
| /linux-6.12.1/drivers/soc/hisilicon/ |
| D | Kconfig | 12 The Huawei Cache Coherence System (HCCS) is a multi-chip
|
| /linux-6.12.1/arch/arm/mach-mvebu/ |
| D | coherency.c | 72 * The "Shared L2 Present" bit affects the "level of coherence" value
75 * that included in the defined level of coherence. When HW I/O
|
| /linux-6.12.1/Documentation/devicetree/bindings/perf/ |
| D | marvell-cn10k-tad.yaml | 13 The Tag-and-Data units (TADs) maintain coherence and contain CN10K
|
| /linux-6.12.1/arch/powerpc/boot/dts/fsl/ |
| D | e500v1_power_isa.dtsi | 45 power-isa-mmc; // Memory Coherence
|
| D | e500v2_power_isa.dtsi | 45 power-isa-mmc; // Memory Coherence
|
| D | e500mc_power_isa.dtsi | 53 power-isa-mmc; // Memory Coherence
|
| D | e5500_power_isa.dtsi | 53 power-isa-mmc; // Memory Coherence
|
| D | e6500_power_isa.dtsi | 53 power-isa-mmc; // Memory Coherence
|
| /linux-6.12.1/drivers/crypto/ccree/ |
| D | cc_aead.h | 66 /* used to prevent cache coherence problem */
|
1234