Getting this error is normally a side-effect of not having enough RAM. We 12GB
or more to compile gem5 safely.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
It can be resolved by installing the libraries that are missing. How you do so
will different depending on your host system. However, these are just warnings,
not errors. gem5 is still usable for the vast majority of cases without these
libraries. These warnings simply exist to inform the users
I think this is an annoying comment to here, but it means there’s an an
instruction it doesn’t know how to process. In SE mode the error handling is
very unhelpful in telling you what that instruction actually is. I’m almost
certain in this case your compilation is including some ISA extension w
I don’t believe it’s possible to run multiple processes in SE mode. What you
can do is have a single muli-threader process. You could construct a single
binary which utilizes pthreads and have each thread it run something different,
though this could prove difficult to do.
__
What i dont understand here is why do you need cpu switching for starter_fs.py.
Couldn't you juse use starter_fs.py to get the checkpoints you need then load
these checkopoints into a simulation which uses the stdlib?
\
They'll be no easy way of introducing stdlib code like
SimpleSwitchableProc
You’re trying to run a full-system simulation there and that requires
specifying a disk image. The \`src/base/loader/image_file_data.cc:110: fatal:
fatal condition fd < 0 occurred: Failed to open file None.\` error you are
receiving is because you didn’t specify this.
I’d recommend using the ge
Hey James,
\
Perhaps I am very wrong in my assumptions here, but is there any difference in
your idea between a "multiprocessor" setup and a multicore setup? In the gem5
stdlib design each board has one processor, but each processor can have as many
CPUs/Cores as you desire. I don't know the in
Hey Ziyao,
Thank you for pointing this out. This comment is wrong. This was a restriction
at some time, and even then only in the standard library. Right now you can run
multi-threaded applications in se-mode via the \`set_se_binary_workload\`
function. It’s supported.
I’ve submitted a pull-re
