if we have just 1 thread/core and n cores. how would the current functionality
be suited for this? In my implementation, the remaining workloads keep
executing, since we want a multi-workload behaviour. But it makes sure that all
cores reach the max_insts count. Isnt that the expected behaviour?
Sujay
From: Korey Sewell
Sent: Tuesday, June 29, 2010 2:31 PM
To: M5 users mailing list
Subject: Re: [m5-users] running multi-program workloads
withindividualcheckpoints for each program
I can send a patch for this if interested. Has anyone else implemented this?
At some point we had in the tree where when a thread called the exit system
call, the system would check the threadcontexts in the system and only called
"exitSimLoop" if there was only 1 thread active in the system.
I think Steve (?) removed it on a code update given that it's not necessarily
clear that counting the number of threads that are active is a good indicator
of if the workload calling exit should really exit or not. I'm not sure about
the reason, so maybe Steve could comment or a double check of the archives is
in order because I do remember a similar functionality to this inside of M5
previously.
I dont think there was anything about "freezing" stats though. So with regards
to that patch, I guess it wouldnt hurt to post it on reviewboard though so that
people can comment on it and potentially get it into the tree.
--
- Korey
--------------------------------------------------------------------------------
_______________________________________________
m5-users mailing list
m5-users@m5sim.org
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
m5-users@m5sim.org
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
