From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 1/4] monitor: rename out_lock to mon_lock
Date: Thu, 24 May 2018 16:45:48 +0800 [thread overview]
Message-ID: <20180524084548.GE12122@xz-mi> (raw)
In-Reply-To: <877ent8nj3.fsf@dusky.pond.sub.org>
On Thu, May 24, 2018 at 10:29:20AM +0200, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > The out_lock is protecting a few Monitor fields. In the future the
> > monitor code will start to run in multiple threads. We are going to
> > turn it into a bigger lock to protect not only the out buffer but also
> > all the rest.
>
> Hmm, not sure about "all the rest": PATCH 3 marks a member as not
> needing protection. Shall I change this to "most of the rest" when I
> apply?
Of course. :) Please feel free to touch up the commit message where
necessary (this rule applies to all my patches). I fully trust your
wordings.
Thanks!
--
Peter Xu
next prev parent reply other threads:[~2018-05-24 8:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 4:39 [Qemu-devel] [PATCH v7 0/4] monitor: let Monitor be thread safe Peter Xu
2018-05-24 4:39 ` [Qemu-devel] [PATCH v7 1/4] monitor: rename out_lock to mon_lock Peter Xu
2018-05-24 8:29 ` Markus Armbruster
2018-05-24 8:45 ` Peter Xu [this message]
2018-05-24 11:14 ` Markus Armbruster
2018-05-24 4:39 ` [Qemu-devel] [PATCH v7 2/4] monitor: protect mon->fds with mon_lock Peter Xu
2018-05-24 4:39 ` [Qemu-devel] [PATCH v7 3/4] monitor: more comments on lock-free fleids/funcs Peter Xu
2018-05-24 8:08 ` Stefan Hajnoczi
2018-05-24 8:49 ` Peter Xu
2018-05-24 8:41 ` Markus Armbruster
2018-05-24 8:48 ` Peter Xu
2018-05-24 11:16 ` Markus Armbruster
2018-05-28 6:28 ` Peter Xu
2018-05-24 4:39 ` [Qemu-devel] [PATCH v7 4/4] monitor: add lock to protect mon_fdsets Peter Xu
2018-05-24 9:03 ` Markus Armbruster
2018-05-28 7:06 ` Peter Xu
2018-05-28 15:19 ` Markus Armbruster
2018-05-29 5:51 ` Peter Xu
2018-05-24 9:28 ` Stefan Hajnoczi
2018-05-25 3:30 ` Peter Xu
2018-05-25 9:01 ` Stefan Hajnoczi
2018-05-28 6:29 ` Peter Xu
2018-05-24 4:46 ` [Qemu-devel] [PATCH v7 0/4] monitor: let Monitor be thread safe no-reply
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=20180524084548.GE12122@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@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).