Hi Arun, "I started using ruby memory model after reading from gem5 email archive that classic memory does not work with multicore DerivO3CPU.": I didn't know this, where was this mentioned? I have just run an ARM pthread hello world on DerivO3CPU 2 cores and it worked on master.
I reproduce your problem on X86 DerivO3CPU classic but not ARM DerivO3CPU. But a pthread hello world (single binary under --cmd that spanws threads) with 2 CPUs worked, I don't know the cause. If no one knows about this issue, you need to try and debug it :-) I would also open a ticket for this bug at https://gem5.atlassian.net/browse/GEM5 and move all discussion there. On Tue, Feb 18, 2020 at 4:43 AM Arun Kavumkal <arunkp.onl...@gmail.com> wrote: > > Hi, > I am trying to run gem5 in SE mode with number of cpus 2, cpu type > DerivO3CPU, and ruby memory model using following command, but the simulation > does not stop even after results are produced , ie "Hello world!" is printed > to stdout > > build/X86_MESI_Three_Level/gem5.opt configs/example/se.py -n 2 --ruby > --cpu-type=DerivO3CPU -c > 'tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello' > > I started using ruby memory model after reading from gem5 email archive that > classic memory does not work with multicore DerivO3CPU. > > Thanks > Arun KP > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > 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
