MEM: Separate queries for snooping and address ranges
Review Request #948 - Created Dec. 18, 2011 and submitted
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
MEM: Separate queries for snooping and address ranges This patch simplifies the address-range determination mechanism and also unifies the naming across ports and devices. It further splits the queries for determining if a port is snooping and what address ranges it responds to (aiming towards a separation of cache-maintenance ports and pure memory-mapped ports). Default behaviours are such that most ports do not have to define isSnooping, and master ports need not implement getAddrRanges.
util/regress all passing (disregarding t1000 and eio)
Looks great. I think the recvStatusChange() thing was yet another exercise in pointless generality, since we never found a status other than RangeChange. I did notice a couple of places where the comment still says "status change", but that's not a huge deal.
-
src/mem/bus.cc (Diff revision 1) -
Hey, that's not how we spell "neighbor" in these parts ;)