te the sleep cycles to each cpu? Or is just
> sim_ticks - cpu#.numCycles?
>
> Thanks in advance.
>
>
> Obter o Outlook para iOS
>
> De: Ciro Santilli
> Enviado: Monday, October 21, 2019 6:50:37 PM
> Para: gem5 users mailing list ; juninho.u...
in advance.
>
>
> Obter o Outlook para iOS
>
> De: Ciro Santilli
> Enviado: Monday, October 21, 2019 6:50:37 PM
> Para: gem5 users mailing list ; juninho.u...@hotmail.com
>
> Assunto: Re: [gem5-users] stats seem to be wrong in multicore simula
[gem5-users] stats seem to be wrong in multicore simulation using
SE mode
Are the threads waiting for one another e.g. with pthread_join?
This leads to futex syscalls WAIT, which I think make the CPU stop
ticking until WAKE, have a look at futexFunc.
Also try tracing with --debug-flags E
Are the threads waiting for one another e.g. with pthread_join?
This leads to futex syscalls WAIT, which I think make the CPU stop
ticking until WAKE, have a look at futexFunc.
Also try tracing with --debug-flags ExecAll,SyscallBase you should be
able to see CPUs stop tracing after they go to sle
Hi all,
I am running a simulation using Pthreads lib in a four-core processor using SE
mode in gem5. I separate the snippet of the stats file to show my problem, as
can be seen below:
sim_ticks 723694000 #
Number of ticks simulated
syste