| commit | ba59fb778ec68b072196cff9af11c7612a6e52f2 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 13 Jun 2018 12:23:08 +0000 (13 14:23 +0200) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Thu, 28 Jun 2018 17:05:32 +0000 (28 19:05 +0200) | ||
| tree | ed0008190d1ecec2102d9f506a879f2e119a930b | treesnapshot (tar.gz zip) |
| parent | f1aff7aa8e6f238909bd0b0e7a1fe235802843f2 | commitdiff |
QemuMutex: support --enable-debug-mutex
We have had some tracing tools for mutex but it's not easy to use them
for e.g. dead locks. Let's provide "--enable-debug-mutex" parameter
when configure to allow QemuMutex to store the last owner that took
specific lock. It will be easy to use this tool to debug deadlocks
since we can directly know who took the lock then as long as we can have
a debugger attached to the process.
Reviewed-by: Emilio G. Cota <cota@braap.org>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180425025459.5258-4-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
We have had some tracing tools for mutex but it's not easy to use them
for e.g. dead locks. Let's provide "--enable-debug-mutex" parameter
when configure to allow QemuMutex to store the last owner that took
specific lock. It will be easy to use this tool to debug deadlocks
since we can directly know who took the lock then as long as we can have
a debugger attached to the process.
Reviewed-by: Emilio G. Cota <cota@braap.org>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180425025459.5258-4-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| configure | diffblobblamehistory | |
| include/qemu/thread-posix.h | diffblobblamehistory | |
| include/qemu/thread-win32.h | diffblobblamehistory | |
| util/qemu-thread-common.h | diffblobblamehistory |