I would guess the exit() call that hello world is performing is
exitGroup not exit (I don't know why) which causes all threads to exit.


Ali 

On 07.01.2013 09:03, Payne, Benjamin wrote: 

> Hello, 
> 
>
Could you post the commands you are using to perform the tasks you
describe? 
> 
> Also, if it's not too big, the output status messages
from the gem5 run. 
> 
> Thanks, 
> 
> Ben 
> 
> FROM:
gem5-users-boun...@gem5.org [mailto:gem5-users-boun...@gem5.org] ON
BEHALF OF mehmet basaran
> SENT: Sunday, January 06, 2013 6:08 PM
> TO:
gem5-users@gem5.org
> SUBJECT: [gem5-users] Weird behavior when running
different [independent] workloads on multicores 
> 
> Hi all,
> 
> I
have configured a CPU with 6 cores. I use queen benchmark and simple
hello world code.
> 
> - When I run queen benchmark (with different
parameters) on all the cores, each process ends naturally, I get the
correct output.
> - But when I run queen benchmark on 5 cores and hello
world code on the remaining one core, gem5 terminates before 5 cores
(queen bench) finishes execution. 
> 
> I checked to see if this is
about the time difference required by the each workload. I used queen
benchmark for all 6 cores, but gave one core much smaller workload.
Still all the cores finished their jobs before gem5 terminated.
> 
>
Should I configure something before running different binaries for each
processor? Pointers, answers, help or even questions are most welcome.
>

> Thanks
> Mehmet 
> 
>
_______________________________________________
> gem5-users mailing
list
> gem5-users@gem5.org
>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users [1]




Links:
------
[1]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to