Hello Everyone, Just an update, I was able to avoid this problem by using gem5_amd ( https://gem5.googlesource.com/amd/gem5/), I tried using the same se.py file used in gem5_amd but still, the master (https://github.com/gem5/gem5) *O3CPU* is broken and multi-programmed workload simulation just goes in never-ending phase.
Jason: I think there is a problem with O3CPU files because other CPUs work correctly if there was se.py file problem, the gem5_amd's se.py file would have solved the problem. Whenever you get time please look into this issue. I did not see a multi-programmed workload using SE as an agenda for the upcoming stable gem5_19 version. Is there a way that we can put this as "ToDo" for future release? Due to someone's commit, the support for the muti-workload program is broken. Or maybe I am using se.py not correctly. Best regards, Abhishek On Thu, Feb 6, 2020 at 10:46 AM Abhishek Singh < abhishek.singh199...@gmail.com> wrote: > Hi Giacomo, > > I tried your suggestion of using ( ";"), without SMT and trying > multi-programmed workload simulation. > I thought to test it using the hello world example, and I found some > problems with se.py file > > My command line is > *./build/X86/gem5.fast configs/example/se.py -c > "tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello" > --caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB > --l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64 > --cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB > --sys-clock='2.6GHz' --cpu-clock='2.6GHz' -n 2* > > When I run this command the simulation prints "Hello World" twice but do > not exit simulation, the longest it ran was 59 minutes in fast mode and > there was no exit statement printed and no m5out file generated. Is there > anything else I am missing? > > > Jason, as you pointed this can be a problem with se.py file, can you > double-check it by testing, if that's the case then either a quick fix else > a comment line specifying limitation of se.py file should be included > within se.py file. > Carlos Escuin, there was no "Switch.cpu", thanks for your reply > > Best regards, > > Abhishek > > > On Wed, Feb 5, 2020 at 11:40 AM Giacomo Travaglini < > giacomo.travagl...@arm.com> wrote: > >> This is a nasty thing: >> >> get_processes(options) in se.py is manually parsing the workload list. >> >> This shouldn't happen; we should explicitly enable argument lists without >> coming up with a custom made ";" separeted synthax. >> >> Giacomo >> ------------------------------ >> *From:* gem5-users <gem5-users-boun...@gem5.org> on behalf of Giacomo >> Travaglini <giacomo.travagl...@arm.com> >> *Sent:* 05 February 2020 16:36 >> *To:* gem5 users mailing list <gem5-users@gem5.org> >> *Subject:* Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error >> using SMT >> >> ./build/X86/gem5.opt configs/example/se.py -c >> *tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello* >> --caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB >> --l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64 >> --cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB >> --sys-clock='2.6GHz' --cpu-clock='2.6GHz' --smt >> >> The bolded argument (more specifically the ";") is confusing the >> OptParser. >> You should quote it >> >> ./build/X86/gem5.opt configs/example/se.py -c* "* >> tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello >> *"* --caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB >> --l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64 >> --cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB >> --sys-clock='2.6GHz' --cpu-clock='2.6GHz' --smt >> ------------------------------ >> *From:* gem5-users <gem5-users-boun...@gem5.org> on behalf of Abhishek >> Singh <abhishek.singh199...@gmail.com> >> *Sent:* 05 February 2020 16:14 >> *To:* gem5 users mailing list <gem5-users@gem5.org> >> *Subject:* [gem5-users] MultiProgrammed Workload X86 O3CPU error using >> SMT >> >> Hello Everyone, >> >> I am using X86 ISA, Out of order CPU. I wanted to run a multi-programmed >> workload using SMT >> >> My command line 1 is: >> >> ./build/X86/gem5.opt configs/example/se.py -c >> tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello >> --caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB >> --l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64 >> --cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB >> --sys-clock='2.6GHz' --cpu-clock='2.6GHz' --smt >> >> >> I am using commit *82f6d6e90.* >> >> When I run the command and check *m5out/config.ini, *the *system.cpu* >> parameter is AtomicSimpleCPU instead of DerivO3CPU. >> >> I tried the command without smt and using "-n" to run on different cores >> >> My command line 2 is: >> ./build/X86/gem5.opt configs/example/se.py -c >> tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello >> --caches --l2cache --l1d_size=32kB --l1i_size=32kB --l2_size=2MB >> --l1d_assoc=8 --l1i_assoc=8 --l2_assoc=16 --cacheline_size=64 >> --cpu-type=DerivO3CPU --mem-type=DDR4_2400_8x8 --mem-size=8GB >> --sys-clock='2.6GHz' --cpu-clock='2.6GHz' -n 2 >> >> The cpu being used is AtomicSimpleCPU instead O3CPU indicated by >> m5out/config.ini, is there any problem with my command or is there an error? >> >> Best regards, >> >> Abhishek >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose the >> contents to any other person, use it for any purpose, or store or copy the >> information in any medium. Thank you. >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose the >> contents to any other person, use it for any purpose, or store or copy the >> information in any medium. Thank you. >> _______________________________________________ >> 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
