The --trace-start option lets you start tracing at a particular simulation tick; if you know when boot completes, then you can set that appropriately.
In theory you could add an m5op to enable tracing and then call that from your init script, or something like that, but that's only worth the effort if you're going to be doing this a lot. Steve On Wed, Nov 2, 2011 at 1:59 PM, Dibakar Gope <[email protected]> wrote: > Hi All, > > I am trying to get selective traces for the branch predictors at fetch, > decode and iew stage for ALPHA_FS O3 system. In order to do that, I have > enabled --debug-flags=Exec (with turning-off the non-required switches) and > retain the DPRINTFs in src/cpu/o3/fetch_impl.hh,decode_impl.hh,iew_impl.hh > that I felt necessary . However, I want the trace to start after the kernel > is booted-up. Looking at the Trace Options switches, I could not find an > option which can start tracing after linux boot-up. Is there an option in > gem5, through which I can start the trace after kernel boot-up? > > Thanks, > Dibakar Gope > PhD Student, UW-Madison > _______________________________________________ > 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
