[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] tracetool: Include thread id information in log
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH] tracetool: Include thread id information in log backend |
Date: |
Mon, 5 Nov 2018 09:18:31 +0000 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Thu, Oct 04, 2018 at 11:30:09AM -0300, Fabiano Rosas wrote:
> 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.:
>
> address@hidden:qemu_mutex_lock waiting on mutex 0x1103ee60
> (/root/qemu/util/main-loop.c:236)
> ...
> address@hidden:qemu_mutex_unlock released mutex 0x1103ee60
> (/root/qemu/cpus.c:1238)
> address@hidden: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 <address@hidden>
> Signed-off-by: Fabiano Rosas <address@hidden>
> ---
> scripts/tracetool/backend/log.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my tracing-next tree:
https://github.com/stefanha/qemu/commits/tracing-next
Stefan
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] [PATCH] tracetool: Include thread id information in log backend,
Stefan Hajnoczi <=