Hi Khaled,
We also found this problem when using checkpoints and switching CPUs to
the MinorCPU model. The workaround we found was to comment out the
"activateContext(0);" on line 195 of src/cpu/minor/cpu.cc and the
"threads[0]->activate();" on line 201, both in MinorCPU::startup().
That breaks being able to start up with a MinorCPU without a switch, but
should allow you to simulate the switch correctly.
Thanks,
Sam
On 2015-12-02 16:18, Andreas Hansson wrote:
Hi Khaled,
It would be good if you could run with gdb and see what is going
wrong.
Andreas
From: Khaled Attia <[email protected]>
Date: Wednesday, 2 December 2015 at 15:59
To: Andreas Hansson <[email protected]>, gem5 users mailing
list <[email protected]>
Subject: Re: [gem5-users] Problem with using MinorCPU in ARM
full-system
Hello Andreas,
The error happens when I try to switch from the atomicsimple mode to
minorcpu model. (By modifying the switch_cpu list in simulation.py in
the event of fast-forward). Whenever the list contains any CPU of the
minorCPU model, I got the segmentation fault, core dumped error and
gem5 exits. I tried using derivo3cpu and timingsimplecpu and both work
fine.
Regards, IMPORTANT NOTICE: The contents of this email and any
attachments are confidential and may also be privileged. If you are
not the intended recipient, please notify the sender immediately and
do not disclose the contents to any other person, use it for any
purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
