Hi Joel,
The problem of restoring from the checkpoint is solved by recollecting the
checkpoint, this time without attaching a terminal. Thanks for your help.
Best regards,
Azadeh
On Sat, Jul 2, 2016 at 8:40 PM, Azadeh Shirvanian <
azadeh.shirvan...@gmail.com> wrote:
> Hi Joel,
>
> I see... Th
Hi Joel,
I see... Thank you! I will try it and will write about the result.
Best regards,
Azadeh
On Sat, Jul 2, 2016 at 7:10 PM, Joel Hestness wrote:
> Hi Azadeh,
> I just realized what might be going on. It looks like you attached a
> terminal during your simulation to collect the checkpoin
Hi Azadeh,
I just realized what might be going on. It looks like you attached a
terminal during your simulation to collect the checkpoint (bolded in your
checkpoint sim output snippet below):
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
REAL SIMULATION
info:
Dear Joel and Ayaz,
Thanks for your replies. I think there are two issues now. One is about
restoring from the checkpoint.
Regarding your questions, Joel, *cjpeg.rcS* contains the following:
#!/bin/sh
cd /jpeg/jpeg-6a
./cjpeg -outfile ../gm.jpg ../input.ppm
/sbin/m5 exit
/sbin/m5 exit
It only
Hi Azadeh,
I'm still not sure what could be going wrong. Note that gem5 does not
write to disk images, so you won't see simulation output (unless you attach
a terminal to the simulated system after running the benchmark in FS mode
and browse the image from the simulator).
Here are a couple more
Azadeh: Regarding output JPEG file on disk image, due to COW functionality
Simulation does not change the contents of disk image. So, once you are
done with simulation you cannot see output files on disk image unless you
turn off the COW layer.
On Fri, Jul 1, 2016 at 3:09 PM, Azadeh Shirvanian <
Hi Jason,
Thank you for the important point about the options --restore-with-cpu and
--cpu-type.
And yes, I looked at the terminal output (using m5term) for the main
simulation after restoring from the checkpoint and I don't see anything
there. As I wrote at the end of my last email, the file
*sy
Hi Azadeh,
I'm not certain what the problem is. However, you don't have to use the O3
CPU to "restore-with". That option is the CPU that is used during
checkpoint restore, not the CPU used once checkpoint restore is complete on
the main simulation. To choose which CPU to use for the main simulatio
Dear all,
I have got stuck somewhere regarding checkpoints. What I need to do is
running an image processing application, which takes an image as the input
and produces an image as the output, in full system mode and with X86.
I used *hack_back_ckpt.rcS* to create a checkpoint after booting Linux
