There isn't any support for this at the moment, but you could add it. If you know the cycle in which your benchmark is going to run you can also start collection with --trace-start=.
Ali On Mar 13, 2013, at 10:08 PM, huangyongbing <huangyongb...@ncic.ac.cn> wrote: > Hi all, > > I want to collect instruction traces belonged to a specific binary. > As I know, if some necessary debug flags such as “debug::execenable”, > “trace:enabled” are set in gem5, the traceInst function will be called and > start to collect the instruction traces. So my question is that, are there > any triggers at runtime to set or reset these debug flags? For example, if a > m5 operation can modify the debug flags, I can call the m5 operation before > and after executing a specific binary which then start and stop collecting > trace correspondingly. > > Thanks! > > Best regards, > > Yongbing Huang > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
