Hello Fernando, Thank you for your response. As you had written, I grepped "/sbin/m5 readfile" in my disk image, but there seemed to be no problem.
However, the problem is solved meanwhile. It was the issue of time. I only needed to exit the simulation at a later time using delay ticks. I modified the script cjpeg.rcS and used the --script option again in the command line. The JPEG image was then fully created and stored to the disk image (meaning that it was available in the disk image even after the simulation was complete). Best regards, Azadeh On Fri, Jul 8, 2016 at 4:49 PM, Fernando Endo <[email protected]> wrote: > Hello, > > It seems to be a bug for me. Try to grep "/sbin/m5 readfile" in your gem5 > disk image, e.g., inside aarch64-ubuntu-trusty-headless.img it is at > /etc/init/tty1.conf. That command loads the script passed with --script, so > maybe the bug is by there. > > Hope it helps, > > -- > Fernando A. Endo, Post-doc > > INRIA Rennes-Bretagne Atlantique > France > > > 2016-07-08 14:02 GMT+02:00 Azadeh Shirvanian <[email protected]> > : > >> Hi, >> >> I'm sorry that I'm writing about this problem again, but I have to >> because we weren't able to solve the issue and proceed with the study so >> far. >> >> As I have written in detail in my previous email in the current thread, I >> have turned off the COW layer in order to store the output of an image >> processing application on the disk image after the simulation. Although I >> have done this, the output is stored on the disk image only when I don't >> use the --script option in the command line. What I need is having the >> output stored on the disk image also when I use the --script option. >> This means that currently, in this case, the disk image doesn't keep the >> output. >> >> I hope there is a solution to this problem and that someone would share >> that (or any idea) with me. :) >> >> I would be really thankful. >> >> Azadeh >> >> On Tue, Jul 5, 2016 at 9:53 PM, Azadeh Shirvanian < >> [email protected]> wrote: >> >>> Dear all, >>> >>> As I have written in another thread, I need to run an image processing >>> application in full system mode using caches and O3 CPU. The ISA is X86. >>> The application creates a JPEG image as its output, which I need to find on >>> the disk image after the simulation is terminated. >>> >>> For this purpose, I have turned off the COW layer in FSConfig.py. as it >>> follows: >>> >>> class RawIdeDisk(IdeDisk): >>> image = RawDiskImage(read_only=False) >>> def childImage(self, ci): >>> self.image.image_file=ci >>> >>> #class CowIdeDisk(IdeDisk): >>> # image = CowDiskImage(child=RawDiskImage(read_only=True), >>> # read_only=False) >>> >>> # def childImage(self, ci): >>> # self.image.child.image_file = ci >>> >>> And inside def makeX86System: >>> >>> # disk0 = CowIdeDisk(driveID='master') >>> # disk2 = CowIdeDisk(driveID='master') >>> disk0 = RawIdeDisk(driveID='master') >>> disk2 = RawIdeDisk(driveID='master') >>> >>> I disregarded the options such as --caches and --cpu-type and tried >>> running the simulation, and I observed that the output JPEG image is stored >>> on the disk image only when I don't use the --script option and execute >>> the commands of the script (called cjpeg.rcS) in an attached terminal >>> instead. Otherwise, when I use the option >>> --script=configs/boot/cjpeg.rcS, the created JPEG image is not stored >>> on the disk image. >>> >>> My question is how I can have the JPEG image stored on the disk image in >>> the latter case too. >>> >>> I would appreciate any help or idea. >>> >>> Azadeh >>> >>> >> >> _______________________________________________ >> 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 >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
