aboutsummaryrefslogtreecommitdiff
path: root/trace/control-internal.h
diff options
context:
space:
mode:
authorFabiano Rosas <farosas@linux.ibm.com>2018-10-04 11:30:09 -0300
committerStefan Hajnoczi <stefanha@redhat.com>2018-12-12 10:04:59 +0000
commit8fbc12f324135cf579277c212ab8690ca9174512 (patch)
tree0a4254806de40757f9a0af0b8d86c5e3cf804ee0 /trace/control-internal.h
parentbb9bf94b3e8926553290bc9a7cb84315af422086 (diff)
tracetool: Include thread id information in log backend
Currently the log backend prints the process id of QEMU at the start of each output line, but since threads share the same PID there is no clear distinction between their outputs. Having the thread id present in the log makes it easier to see when output comes from different threads. E.g.: 12423@1538597569.672527:qemu_mutex_lock waiting on mutex 0x1103ee60 (/root/qemu/util/main-loop.c:236) ... 12430@1538597569.503928:qemu_mutex_unlock released mutex 0x1103ee60 (/root/qemu/cpus.c:1238) 12431@1538597569.503937:qemu_mutex_locked taken mutex 0x1103ee60 (/root/qemu/cpus.c:1257) ^here In the above, 12423 is the main process id and 12430 & 12431 are the two vcpu threads. (qemu) info cpus * CPU #0: thread_id=12430 CPU #1: thread_id=12431 Suggested-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com> Signed-off-by: Fabiano Rosas <farosas@linux.ibm.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'trace/control-internal.h')
0 files changed, 0 insertions, 0 deletions