Dude, you and Gabe really need to learn to prune the text that you're quoting.
> I think actually, we're loosing the memory ever time we call simulate() so > the simulator doesn't actually need to exit even. If you're returning to > python to change something/switch cpus and then simulate again a new limit > event is created each time. I imagine we loose the memory if the limit_event > == se_event or not (does python free it)? Yes, I think we do lose memory. We could make python responsible for freeing it, though that might get messy since python has it's own concept of garbage collection. We could make simulate a class and make limit_event and se_event members (and reschedule as you mentioned). We could also just make them globals. Perhaps we need to have a subclass of EventQueue that handles this stuff. Steve should probably chime in since he is toying around with parallel event queues. > For the case with the hack in it now, wouldn't something like rescheduling > it to the current tick, and setting auto delete (it seems like there is no > method to actually do this though) be better? AutoDelete is a flag. Just call limit_event.setFlags(AutoDelete); Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
