On Mon, Jun 16, 2008 at 8:49 AM, nathan binkert <[EMAIL PROTECTED]> wrote: >> I don't think this works, given that you've (still) got a single >> global static instance of DefaultPeerPort... right? I ask because >> this patch looks frighteningly familiar... I just did the same thing >> last week (including the identical class rename :-) ) but mine was >> more complicated because I dynamically allocated a new DefaultPeerPort >> instance for every port so that each one could keep the right peer >> pointer. > > By not work, how do you mean? It did fix my problems. The real > problem for me was in how the switchover was handled. >
I was specifically talking about the error message that I quoted in my earlier response. Since there's only one global static instance, the 'peer' field will point to the last initialized port, so the error message will reflect that regardless of which port is actually unconnected. Steve _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
