riscv/qemu: QEMU main repository: Please see https://www.qemu.org/docs/master/devel/submitting-a-patch.html for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website. http://www.qemu.org - qemu

QEMU main repository: Please see https://www.qemu.org/docs/master/devel/submitting-a-patch.html for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website. http://www.qemu.org

Tree: c314e50b8a

History

Fabiano Rosas 8fbc12f324 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>		8 years ago
..
__init__.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago
dtrace.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago
ftrace.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago
log.py	tracetool: Include thread id information in log backend	7 years ago
simple.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago
syslog.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago
ust.py	trace: add TRACE_<event>_BACKEND_DSTATE()	9 years ago