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
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
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:
Hi Andrea,
I can't get my microbenchmark to run with gem5. If I execute it without
sudo, I get a "Can't open /dev/mem: Permission denied". If I execute it
with sudo on its own, it seems to finish fine. But when I want to execute
it with gem5, I get a segfault.
"warn: mmap: writing to shared mmap
Hi Victor,
I use checkpoints with SE.py , can you describe your problem?
Is it related to the various “—work-{begin | end}-*” parameters in Options.py?
Il giorno 10 giu 2019, alle ore 12:43, Victor Kariofillis
mailto:vickariofil...@gmail.com>> ha scritto:
Hi,
I have already implemented pseudo
