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 v5 3/4] monitor: more comments on lock-free fleids/funcs
Date: Fri, 18 May 2018 18:21:43 +0800 [thread overview]
Message-ID: <20180518102143.GO2569@xz-mi> (raw)
In-Reply-To: <87zi0ylaab.fsf@dusky.pond.sub.org>
On Thu, May 17, 2018 at 02:46:36PM +0200, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > Add some explicit comment for both Readline and cpu_set/cpu_get helpers
> > that they do not need the mon_lock protection.
>
> Appreciated!
>
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > monitor.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/monitor.c b/monitor.c
> > index d6c3c08932..ae5bca9d7c 100644
> > --- a/monitor.c
> > +++ b/monitor.c
> > @@ -207,7 +207,7 @@ struct Monitor {
> > int suspend_cnt; /* Needs to be accessed atomically */
> > bool skip_flush;
> > bool use_io_thr;
> > - ReadLineState *rs;
> > + ReadLineState *rs; /* Only used in parser, so no lock needed. */
>
> Pardon the ignorant question: why does "only used in parser" imply "no
> lock needed"?
Since even if the monitors can be run in multiple threads now, the
monitor parser of a specific Monitor will still only be run in either
the main thread or the monitor iothread. My fault to be unclear on
the comment. Maybe this one is better:
It is only used in parser, and the parser of a monitor will only be
run either in main thread or monitor IOThread but never both, so no
lock is needed when accessing ReadLineState.
>
> > MonitorQMP qmp;
> > gchar *mon_cpu_path;
> > BlockCompletionFunc *password_completion_cb;
> > @@ -1313,7 +1313,7 @@ void qmp_qmp_capabilities(bool has_enable, QMPCapabilityList *enable,
> > cur_mon->qmp.commands = &qmp_commands;
> > }
> >
> > -/* set the current CPU defined by the user */
> > +/* set the current CPU defined by the user. BQL needed. */
>
> It's okay to start a comment containing a phrase with a lower case
> letter, but you're turning this one into two sentences, and sentences
> start in upper case. Can touch up on commit.
>
> "BQL needed" is okay, just a bit terse; I'd write "Caller must hold
> BQL". Could change that, too.
I'll do that.
>
> > int monitor_set_cpu(int cpu_index)
> > {
> > CPUState *cpu;
> > @@ -1327,6 +1327,7 @@ int monitor_set_cpu(int cpu_index)
> > return 0;
> > }
> >
> > +/* BQL neeeded. */
>
> Likewise.
Will do. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-05-18 10:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 4:17 [Qemu-devel] [PATCH v5 0/4] monitor: let Monitor be thread safe Peter Xu
2018-05-09 4:17 ` [Qemu-devel] [PATCH v5 1/4] monitor: rename out_lock to mon_lock Peter Xu
2018-05-17 12:32 ` Markus Armbruster
2018-05-18 10:15 ` Peter Xu
2018-05-09 4:17 ` [Qemu-devel] [PATCH v5 2/4] monitor: protect mon->fds with mon_lock Peter Xu
2018-05-10 10:11 ` Stefan Hajnoczi
2018-05-17 12:47 ` Markus Armbruster
2018-05-09 4:17 ` [Qemu-devel] [PATCH v5 3/4] monitor: more comments on lock-free fleids/funcs Peter Xu
2018-05-10 10:12 ` Stefan Hajnoczi
2018-05-17 12:46 ` Markus Armbruster
2018-05-18 10:21 ` Peter Xu [this message]
2018-05-23 8:29 ` Markus Armbruster
2018-05-23 8:47 ` Peter Xu
2018-05-23 15:15 ` Markus Armbruster
2018-05-24 4:37 ` Peter Xu
2018-05-09 4:17 ` [Qemu-devel] [PATCH v5 4/4] monitor: add lock to protect mon_fdsets Peter Xu
2018-05-17 13:03 ` Markus Armbruster
2018-05-18 10:53 ` Peter Xu
2018-05-18 12:27 ` Markus Armbruster
2018-05-21 5:18 ` Peter Xu
2018-05-23 8:39 ` Markus Armbruster
2018-05-23 8:52 ` 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=20180518102143.GO2569@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).