> > Yea, it should definitely be a parameter... maybe a system parameter > rather than a workload parameter though (since in multi-programmed workloads > you actually have multiple workload objects). > I actually spoke to soon about this fix. Right now, I'm going through a bunch of minor changes that now have to use the System object to get this to work right.
In SE mode, M5 doesnt bother to do anything to bind the thread contexts with the system since it's assumed you dont need it. So I am trying to get that fixed so that a ThreadContext object can use it's system pointer to look through all the threads/cpus in a system and see if all of them are "unallocated" before exiting the simulation.... The difference between the process and system registerThreadContext() functions is slight enough where it confuses me, since this function assigns an ID for the CPU. I'm trying to figure out why a Process would need a vector of thread contexts and I'm wondering if we can just use the FS way of assigning ids in SE. Anyway, I'll have to send out a patch I guess before it gets pushed in the tree, so stay tuned... -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
