On Mar 6, 2010, at 5:41 PM, Stijn Souffriau wrote: > Hi, > > So I've written a fancy deadlock-detection algorithm hoping that it > would > detect deadlocks caused the l2-bus trying to access a private cache > while that > same private cache tried to access the l2-bus, so that I could roll > back one > of the calls. However I found an additional problem. It appears > that the > private caches call the port interface of their CPU's as well which > I didn't > expect to happen. What are the caches doing? If you provide us with a back trace of the call we could tell you for sure, but I imagine it's either a response coming back from the cache, or it could be one of the status change messages (I think the only one we support is the range change) that happens at boot and when PCI devices get their address ranges assigned by the kernel. If it's the latter it should be harmless.
Ali _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
