Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-10 Thread Abhishek Singh
With that said For x86 O3CPU, the multi program workload simulation is also broken. So basically one can not multi core simulation using x86 O3CPU with and without SMT. Also, to all developers who push commit to gem5, please do thorough testing as both of this support was working in older commits!

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-10 Thread Kevin Loughlin
Hi all, I believe there is indeed at least one bug in O3 CPU implementation when using SMT in SE mode. Namely, the rename mapping for the zero register on additional threads fails assert(prev_reg->isZeroReg()) in rename() in /src/cpu/o3/rename_map.cc. This is because the processor logic does not c

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-06 Thread Abhishek Singh
without >> coming up with a custom made ";" separeted synthax. >> >> Giacomo >> -- >> *From:* gem5-users on behalf of Giacomo >> Travaglini >> *Sent:* 05 February 2020 16:36 >> *To:* gem5 users mailing list

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-06 Thread Abhishek Singh
plicitly enable argument lists without > coming up with a custom made ";" separeted synthax. > > Giacomo > -- > *From:* gem5-users on behalf of Giacomo > Travaglini > *Sent:* 05 February 2020 16:36 > *To:* gem5 users mailing list > *S

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-05 Thread Carlos Escuin
Hi Abhishek, I think when you check *m5out/config.ini*, you should look at *switch.cpu* instead of *system.cpu*. System.cpu is always initialized to AtomicSimpleCPU by se.py. Switch.cpu is the one you indicate in options and the one whose stats you should be looking at. System.cpu instruc

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-05 Thread Giacomo Travaglini
s on behalf of Giacomo Travaglini Sent: 05 February 2020 16:36 To: gem5 users mailing list 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/

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-05 Thread Jason Lowe-Power
Hi Abhishek, SMT is not something that is normally tested. I expect that this is a problem with se.py (and the 10s of other python files that it uses...). I suggest making a config script from scratch like in Learning gem5 so you know exactly what configuration you're running. You should be able t

Re: [gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-05 Thread Giacomo Travaglini
x27; --smt From: gem5-users on behalf of Abhishek Singh Sent: 05 February 2020 16:14 To: gem5 users mailing list 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

[gem5-users] MultiProgrammed Workload X86 O3CPU error using SMT

2020-02-05 Thread Abhishek Singh
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