Hi Øivind, I would check out the documentation on the TraceCPU: http://www.gem5.org/documentation/general_docs/cpu_models/TraceCPU. I think that page describes how to capture the traces.
Cheers, Jaosn On Wed, May 6, 2020 at 12:53 PM Øivind Harket Bakke via gem5-users < gem5-users@gem5.org> wrote: > Hi all, > > I'm currently trying to export traces from a simulation, but I'm only > interested in the instructions that are being simulated. I compare the > stats file (# of simulated instructions) to the traces and they don't match > in size. I've tried to figure out which are the excessive lines in order > filter them out. So my question is as follows: How would I proceed to get > traces of the instructions only? > > Here's the command I run: > ./build/ARM/gem5.opt --debug-flags=Exec,-ExecMacro --debug-file=trace.out > -d configs/Forschung/arm/1G-500M/ configs/Forschung/arm/starter_se.py > --cpu="hpi_nL" --cpu-freq="1GHz" tests/test-progs/hello/bin/arm/linux/hello > > For clearification, the config file is a copy of the one in arm examples, > just adding a HPI model without L2 caches.(hpi_nL) > I've checked out the --debug-help option, but as far as I could tell, > there were no flags to remove from Exec or other flags to enable in order > to reach my goal. > > > Thanks in advance, > Øivind Harket Bakke > _______________________________________________ > 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
_______________________________________________ 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
