| commit | dd9fe29c80b8a35f12d98928a97be3aded80cf69 | |
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Tue, 20 Jan 2015 09:41:15 +0000 (20 09:41 +0000) | ||
| committer | Stefan Hajnoczi <stefanha@redhat.com> | |
| Fri, 6 Feb 2015 10:27:22 +0000 (6 10:27 +0000) | ||
| tree | 1dd36451cb2c4f425607b6472626c4376f79a6d0 | treesnapshot (tar.gz zip) |
| parent | 16017c48547960539fcadb1f91d252124f442482 | commitdiff |
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>
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>
| scripts/tracetool/backend/stderr.py | diffblobblamehistory |