From: "Emilio G. Cota" <cota@braap.org>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 3/4] QemuMutex: support --enable-debug-mutex
Date: Tue, 24 Apr 2018 11:47:30 -0400 [thread overview]
Message-ID: <20180424154730.GB22209@flamenco> (raw)
In-Reply-To: <20180424045112.12963-4-peterx@redhat.com>
On Tue, Apr 24, 2018 at 12:51:11 +0800, Peter Xu wrote:
> 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.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Emilio G. Cota <cota@braap.org>
E.
next prev parent reply other threads:[~2018-04-24 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 4:51 [Qemu-devel] [PATCH v5 0/4] qemu-thread: support --enable-debug-mutex Peter Xu
2018-04-24 4:51 ` [Qemu-devel] [PATCH v5 1/4] tests/atomic_add-bench: add -m option to use mutexes Peter Xu
2018-04-24 4:51 ` [Qemu-devel] [PATCH v5 2/4] qemu-thread: introduce qemu-thread-common.h Peter Xu
2018-04-24 15:46 ` Emilio G. Cota
2018-04-24 4:51 ` [Qemu-devel] [PATCH v5 3/4] QemuMutex: support --enable-debug-mutex Peter Xu
2018-04-24 15:47 ` Emilio G. Cota [this message]
2018-04-24 4:51 ` [Qemu-devel] [PATCH v5 4/4] configure: enable debug-mutex if debug enabled Peter Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180424154730.GB22209@flamenco \
--to=cota@braap.org \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.