Hello,
If you're not doing so already, I'd recommend to start with a known working
configuration and incrementally change it toward your desired system. Then
it'd be easier to report what piece of configuration is not working.
Hope it helps,
--
Fernando A. Endo, PhD student and researcher
Hello,
It seems to be a Linux kernel panic message, not a gem5 error. If that is
the case, and if gem5 supports the feature, you should recompile the Linux
kernel with the right option. Recompiling a kernel my be painful if you've
never done that.
Regards,
--
Fernando A. Endo, PhD student and
Hello,
Not sure if the following ideas works.
You could determine how long OS command are executed after the checkpoint
and run a resetstats (eventually with a delay).
You could try to use the fast forward flag (-F $INSTRUCTIONS) or the cache
warming one, to fast-forward.
Best regards,
--
Thank you Fernando!
Best Regards,
Kumail Ahmed
M.Sc. Student
TU Kaiserslautern
On Sat, Apr 4, 2015 at 2:14 PM, Fernando Endo fernando.en...@gmail.com
wrote:
Hello,
I think that happens because usually gem5 in FS is used to boot Linux, so
they considered that there is always a disk with a
Hello,
I think that happens because usually gem5 in FS is used to boot Linux, so
they considered that there is always a disk with a file system! I never
tried the --bare-metal flags, but I think that if you don't bootstrap the
disk, it is going to be ignored.
Regards,
--
Fernando A. Endo, PhD
Maybe this thesis might give you a hint:
http://www2.imm.dtu.dk/pubdb/views/edoc_download.php/6276/pdf/imm6276.pdf
--
Best Regards,
Kumail Ahmed
M.Sc. Student
TU Kaiserslautern
On Sat, Apr 4, 2015 at 1:25 PM, Fernando Endo fernando.en...@gmail.com
wrote:
Hello,
It seems to be a Linux
Dear All,
I am trying to make Gem5 work with the DVFS as explained in the website.
While running in Atomic Simple it is working as intended but when I change
the cpu type to arm_detailed the simulation crushes during boot. The
message that is shown is the following:
gem5.opt:
