From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Emilio G . Cota" <cota@braap.org>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/3] qemu-thread: support --enable-debug-mutex
Date: Fri, 20 Apr 2018 12:42:09 +0800 [thread overview]
Message-ID: <20180420044212.28765-1-peterx@redhat.com> (raw)
v3:
- note down owner for every locking operations [Emilio]
- let Windows use it too [Emilio]
- added two more patches: patch 1 & 3.
Patch 1 generalize some common hooks for qemu-thread implementation
for both POSIX and Windows.
Patch 2 introduces the new debugging facility.
Patch 3 turns on mutex debugging automatically for "--enable-debug". I
suppose most developers are with that so we naturally benefit from it.
Please review. Thanks.
Peter Xu (3):
qemu-thread: introduce qemu-thread-common.[ch]
QemuMutex: support --enable-debug-mutex
configure: enable debug-mutex if debug enabled
configure | 11 +++++++++++
include/qemu/thread-posix.h | 4 ++++
include/qemu/thread-win32.h | 4 ++++
util/qemu-thread-common.h | 23 +++++++++++++++++++++++
util/qemu-thread-common.c | 38 ++++++++++++++++++++++++++++++++++++++
util/qemu-thread-posix.c | 17 +++++++----------
util/qemu-thread-win32.c | 15 +++++++--------
util/Makefile.objs | 4 ++--
8 files changed, 96 insertions(+), 20 deletions(-)
create mode 100644 util/qemu-thread-common.h
create mode 100644 util/qemu-thread-common.c
--
2.14.3
next reply other threads:[~2018-04-20 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 4:42 Peter Xu [this message]
2018-04-20 4:42 ` [Qemu-devel] [PATCH v3 1/3] qemu-thread: introduce qemu-thread-common.[ch] Peter Xu
2018-04-20 17:07 ` Emilio G. Cota
2018-04-23 5:19 ` Peter Xu
2018-04-20 4:42 ` [Qemu-devel] [PATCH v3 2/3] QemuMutex: support --enable-debug-mutex Peter Xu
2018-04-20 4:42 ` [Qemu-devel] [PATCH v3 3/3] 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=20180420044212.28765-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=cota@braap.org \
--cc=famz@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).