From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "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>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH v10 0/7] monitor: let Monitor be thread safe
Date: Fri, 8 Jun 2018 11:55:04 +0800 [thread overview]
Message-ID: <20180608035511.7439-1-peterx@redhat.com> (raw)
v10:
- collect r-bs
- comment/renice the function monitor_get_clock(), add some commit
message [Stefan, Markus]
v9:
- two more patches to implement Markus's idea to init monitor earlier
(which are patch 5 & 6)
- touch up patch 7 to init the fdset lock in monitor_init_globals()
v8:
- some wording changes according to previous comments [Markus]
- return -ENOENT too in stubs/fdset.c:monitor_fdset_get_fd() [Stefan]
- refactor the fdset functions a bit, drop "ret" where proper [Markus]
- one more patch to fix monitor_lock comment [Markus]
- regular rebase and torturing
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.
Please review. Thanks,
Peter Xu (7):
monitor: rename out_lock to mon_lock
monitor: protect mon->fds with mon_lock
monitor: more comments on lock-free elements
monitor: fix comment for monitor_lock
monitor: remove event_clock_type
monitor: move init global earlier
monitor: add lock to protect mon_fdsets
monitor.c | 168 +++++++++++++++++++++++++++++++++++---------------
stubs/fdset.c | 2 +-
util/osdep.c | 3 +-
vl.c | 7 +--
4 files changed, 121 insertions(+), 59 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-08 3:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 3:55 Peter Xu [this message]
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 1/7] monitor: rename out_lock to mon_lock Peter Xu
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 2/7] monitor: protect mon->fds with mon_lock Peter Xu
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 3/7] monitor: more comments on lock-free elements Peter Xu
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 4/7] monitor: fix comment for monitor_lock Peter Xu
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 5/7] monitor: remove event_clock_type Peter Xu
2018-06-08 5:38 ` Markus Armbruster
2018-06-08 6:24 ` Peter Xu
2018-06-08 7:09 ` Markus Armbruster
2018-06-11 2:42 ` Peter Xu
2018-06-08 13:31 ` Stefan Hajnoczi
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 6/7] monitor: move init global earlier Peter Xu
2018-06-08 3:55 ` [Qemu-devel] [PATCH v10 7/7] monitor: add lock to protect mon_fdsets 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=20180608035511.7439-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 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).