Searched refs:hasSharers (Results 1 - 7 of 7) sorted by relevance
| /gem5/src/mem/cache/ |
| H A D | noncoherent_cache.cc | 190 assert(!bus_pkt->hasSharers());
332 assert(!pkt->hasSharers());
|
| H A D | cache.cc | 96 assert(!pkt->hasSharers());
105 !pkt->hasSharers() &&
113 // would have set hasSharers flag when
121 // (cacheResponding set, hasSharers not set)
545 if (cpu_pkt->hasSharers() && !needsWritable) {
551 DPRINTF(Cache, "%s: passing hasSharers from %s to %s\n",
944 pkt->hasSharers());
1146 panic_if(!invalidate && !pkt->hasSharers(),
1260 bool have_writable = !wb_pkt->hasSharers();
1389 bool pending_modified_resp = !snoop_pkt.hasSharers();
[all...] |
| H A D | base.cc | 956 assert(!pkt->hasSharers());
1166 if (!pkt->hasSharers()) {
1383 assert(!pkt->hasSharers());
1387 // and we start by looking at the hasSharers flag, and ignore the
1393 if (!pkt->hasSharers()) {
1798 bool pending_modified_resp = !pkt->hasSharers() &&
|
| /gem5/src/mem/ |
| H A D | snoop_filter.cc | 284 if (!cpkt->hasSharers()) {
324 if (!cpkt->hasSharers()) {
|
| H A D | packet.hh | 539 // look at the hasSharers flag (if not set, the response is to
577 * On a cache fill (see Cache::handleFill), we check hasSharers
578 * first, ignoring the cacheResponding flag if hasSharers is set.
581 * hasSharers cacheResponding state
595 * On fills, the hasSharers flag is used by the caches in
597 * above. If the hasSharers flag is not set, the packet is passing
601 * The hasSharers flag is also used by upstream caches to inform a
609 * The hasSharers flag is also used on writebacks, in
613 * command hasSharers state
620 bool hasSharers() cons function
[all...] |
| /gem5/src/dev/ |
| H A D | dma_device.cc | 115 !(pkt->cacheResponding() && !pkt->hasSharers()));
|
| /gem5/src/cpu/o3/ |
| H A D | fetch_impl.hh | 1683 !(pkt->cacheResponding() && !pkt->hasSharers()));
|
Completed in 30 milliseconds