Hey Lisa, Is this (below) really something you have to do though? > you'd have to do a lot of configuration in > the python scripts anyway to indicate who is sharing what with whom, and > register that with some common object and make connections to that object.
I mean, as far as my understanding goes, to figure out which ports to snoop, M5 already goes through this type of exploration process (recvStatusChange?). > different levels, e.g. if you had 4 private L1s, 4 private L2s, and 1 shared > L3, walking through and "discovering" how many CPUs exist in the system will > not tell you anything about how they are hooked up together and you'd need a > way in configuration scripts to disambiguate from, say, 4 private L1s, 2 > shared L2s, and 1 shared L3. After everything as been hooked up through the port interface, I think you have enough information. For example, if you have 4 private L1s and 2 shared L2s, then each L2 would ask each of the L1 ports that it's connected to "how many sharers" and then each L1 would ask it's CPU "how many sharers". Eventually, u just sum that information up and pass it back. I understand that might be overkill (over just explicitly setting the sharers), but I dont see how that wouldn't work quite yet (although, I could just be missing something). - Korey _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
