qemu-e2k/scripts/tracetool/backend
Dr. David Alan Gilbert dd9fe29c80 trace: Print PID and time in stderr traces
When debugging migration it's useful to know the PID of
each trace message so you can figure out if it came from the source
or the destination.

Printing the time makes it easy to do latency measurements or timings
between trace points.

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-id: 1421746875-9962-1-git-send-email-dgilbert@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2015-02-06 10:27:22 +00:00
..
__init__.py trace: avoid Python 2.5 all() in tracetool 2014-08-28 13:42:25 +01:00
dtrace.py trace: [tracetool] Minimize the amount of per-backend code 2014-05-07 19:07:18 +02:00
ftrace.py trace: [tracetool] Minimize the amount of per-backend code 2014-05-07 19:07:18 +02:00
simple.py trace: [tracetool] Minimize the amount of per-backend code 2014-05-07 19:07:18 +02:00
stderr.py trace: Print PID and time in stderr traces 2015-02-06 10:27:22 +00:00
ust.py trace: [tracetool] Minimize the amount of per-backend code 2014-05-07 19:07:18 +02:00