Not that I know of. For a poor man's version, since it seems you are just trying to generate various traces from a region of interest.... You could just use the existing m5ops to checkpoint @ the beginning of the region of interest and exit @ the end. That way you could just run from the checkpoint with the trace flags enabled.
Alternatively, I bet it would be possible to define your own m5ops that dynamically enable/disable trace flags. But that would take a bit of work and hacking on the simulator. On Thu, Feb 28, 2013 at 4:25 PM, Umesh Bhaskar <umesh.b2...@gmail.com>wrote: > Hi Gem5 users, > > The command I issued is : > > build/ARM/gem5.debug --debug-flags=Exec configs/example/se.py -c > tests/test-progs/hello/bin/arm/linux/hello > > One line from the trace is shown below: > > 2263500: system.cpu T0 : 0x9cf8.5 : ldr_uop r35, [r34, #16] : MemRead > : D=0x00000000000511fc A=0xbefffcac > > I have a 2 part question > > 1) Is there anyway I can limit the tracing to just the main() or a subset > of instructions inside the main function > and not the preliminary setup instructions ? --trace-start is not very > suitable for this since it is dependent on simulator > ticks > > 2) If this is not possible, can I, in any way, dump the function and data > structure names to the > trace file, so that we can easily filter out information relating to a > subset of instructions. > > Thanks, > Umesh > > > _______________________________________________ > 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
