[gem5-users] Measuring IPC in multi-programmed mode

2019-06-13 Thread Surendra Kumar Shukla
Dear All I want to calculate speedup of running 4 applications in multi-programmed/multiprocessor mode vs running alone in a hypothetical system. For that, I am running 4 benchmarks in 4 separate cores in SE mode. After the completion of the simulation, in the stat.txt file, I am getting IPC for

Re: [gem5-users] Instrumenting ROI in Syscall emulation mode

2019-06-13 Thread Jason Lowe-Power
Hi Victor, Drop the -DM5OP_ADDR define when you're compiling. That will force the m5ops to use the pseudo instruction implementation instead of the MMIO implementation. MMIO is required when using KVM, but no other time. Cheers, Jason On Wed, Jun 12, 2019 at 2:38 PM Victor Kariofillis wrote:

[gem5-users] RISC-V DerivO3CPU: Assertion `atomicOpFunctor != NULL' failed

2019-06-13 Thread Hossein Golestani
Hi, I'm using gem5 for simulation of cross-compiled RISC-V programs. I receive the following error when using the DerivO3CPU model: gem5.opt: build/RISCV/mem/request.hh:678: AtomicOpFunctor* Request::getAtomicOpFunctor(): Assertion `atomicOpFunctor != NULL' failed. I have used this command:

Re: [gem5-users] Instrumenting ROI in Syscall emulation mode

2019-06-13 Thread Victor Kariofillis
Hi Jason, Sadly removing that flag didn't make a difference. I'm still getting an mmap warning (when running it with sudo). I also tried removing the flag (-DM5OP_ADDR=0x) from util/m5/Makefile.x86, but it made no difference. I'm gonna post my changes in case someone is interested. This

[gem5-users] Why is there different results on the stats.txt output file when compared between gem5.perf of different computers?

2019-06-13 Thread Iago .
I am trying to verify computational load of an LQR code on my UAV project, to do so I am using gem5 to simulate different platforms where the code can run. Trying to verify the reproducibility of the test I compiled gem5.perf which I'm using on two different ubuntu computers and when I run the

Re: [gem5-users] Instrumenting ROI in Syscall emulation mode

2019-06-13 Thread Victor Kariofillis
I found the solution. Besides dropping the flag when compiling the microbenchmark as you said, I removed the same flag from the Makefile.x86 and recompiled. Also in the microbenchmark, I removed the incude of m5_mmap.h and calling map_m5_mem() in main. Thanks Jason for the suggestion. On Thu, 13