I'm using the tracing facilities to collect a trace, in this case of
cache accesses, to feed to cache simulators. It's useful if I don't need
timing information but do want to try various cache configurations to
see hit rates. So printing everything from the caches really slows down
simulation, so I'd like to be able to send a signal and not start this
until I need to.
Joe
On 10/6/2010 3:55 AM, Gabe Black wrote:
Why do you want to start tracing at a particular point? Tracing prints
out an instruction trace primarily for debugging, although that basic
system can be extended for other things. You might really want to
trigger collecting statistics.
Gabe
Joe Gross wrote:
Hello,
I wonder if there is some way to easily add signal handling to start
tracing (--trace-start) and to switch cpus (/sbin/m5 switchcpu). I
have a fairly long-running application and I'd really like to be able
to watch it and send the signals when it gets to my region of
interest...it's simpler than recompiling and adding system calls. User
input also affects runtimes, so I can't really set a particular time
to start tracing.
I see that there are a variety of signal handlers in /src/sim/init.cc,
but I'm not sure what to do to perform these actions. Any ideas? Thanks.
Joe
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
