Hi, One way to do it is to use the `--debug-start TICK` option, which will start logging after `TICK` ticks.
To figure out the number of simulated ticks, you can run `/sbin/m5` in the guest right before the ROI, then use `m5.curTick()` in the gem5 system config. The output would be useful if the simulation before reaching the ROI is deterministic; but if the simulation is not, the output would provide a somewhat useful estimation. Regards, Hoa Nguyen On 11/6/20, Hasan, S M Shamimul via gem5-users <gem5-users@gem5.org> wrote: > Hello. > > I am running the Gem5 in full system mode. I am using the following > command. > > =============== > build/X86/gem5.opt --debug-flags=DRAM --debug-file=trace.out > configs/example/fs.py --disk-image="/home/cosmogan-image/cosmogan" > --kernel="/home/gem5/pkr_cp/other/vmlinux-4.9.238" > --script="/home/gem5/pkr_cp/other/tmp.sh" > ================ > > My "tmp.sh" file contains the following code. > ==================================== > #!/bin/sh > /sbin/m5 checkpoint > cd /cosmoGAN/networks > python run_dcgan.py > /sbin/m5 exit > ==================================== > > The problem is the "trace.out" file that I got contains lots of memory > traces that I do not need (e.g., system boot related memory trace). I need > memory traces for only the following code "python run_dcgan.py." How can I > get it? Please let me know. Thanks a lot in advance. > > Sincerely, > S.M.Shamimul Hasan > > > > _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
