From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, "Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] monitor: let Monitor be thread safe
Date: Wed, 18 Apr 2018 17:02:36 +0800 [thread overview]
Message-ID: <20180418090239.13090-1-peterx@redhat.com> (raw)
v2:
- cc correct people... sorry.
Stefan reported this problem that in the future we might start to have
more threads operating on the same Monitor object. This seris try to
add fundamental support for it.
Patch 1 renames the old out_lock to mon_lock, so that it can cover
more things.
Patch 2 uses the mon_lock to protect Monitor object, at least all the
APIs exported in monitor.h
Patch 3 introduces mon_fdsets_lock to protect mon_fdsets global.
Tests: x86 only, make check, raw iotests, windows build.
Please review. Thanks,
Peter Xu (3):
monitor: rename out_lock to mon_lock
monitor: take mon_lock where proper
monitor: add lock to protect mon_fdsets
monitor.c | 120 +++++++++++++++++++++++++++++++++++++++++++++-----------------
1 file changed, 87 insertions(+), 33 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-18 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 9:02 Peter Xu [this message]
2018-04-18 9:02 ` [Qemu-devel] [PATCH v2 1/3] monitor: rename out_lock to mon_lock Peter Xu
2018-04-30 9:56 ` Stefan Hajnoczi
2018-05-02 6:33 ` Peter Xu
2018-04-18 9:02 ` [Qemu-devel] [PATCH v2 2/3] monitor: take mon_lock where proper Peter Xu
2018-04-30 10:10 ` Stefan Hajnoczi
2018-05-02 7:04 ` Peter Xu
2018-04-18 9:02 ` [Qemu-devel] [PATCH v2 3/3] monitor: add lock to protect mon_fdsets Peter Xu
2018-04-30 10:21 ` Stefan Hajnoczi
2018-05-02 7:22 ` 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=20180418090239.13090-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@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.