From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 3/4] monitor: more comments on lock-free fleids/funcs
Date: Thu, 24 May 2018 13:16:11 +0200 [thread overview]
Message-ID: <87bmd55mo4.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20180524084844.GF12122@xz-mi> (Peter Xu's message of "Thu, 24 May 2018 16:48:44 +0800")
Peter Xu <peterx@redhat.com> writes:
> On Thu, May 24, 2018 at 10:41:09AM +0200, Markus Armbruster wrote:
>> Regarding the subject: what are "fleids"?
>
> Ouch. :( I meant the word "fields".
Can touch that up in my tree.
>> 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.
>> >
>> > Signed-off-by: Peter Xu <peterx@redhat.com>
>> > ---
>> > monitor.c | 12 +++++++++++-
>> > 1 file changed, 11 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/monitor.c b/monitor.c
>> > index d6c3c08932..f01589f945 100644
>> > --- a/monitor.c
>> > +++ b/monitor.c
>> > @@ -207,7 +207,16 @@ struct Monitor {
>> > int suspend_cnt; /* Needs to be accessed atomically */
>> > bool skip_flush;
>> > bool use_io_thr;
>> > +
>> > + /*
>> > + * State used only in the thread "owning" the monitor.
>> > + * If @use_io_thr, this is mon_global.mon_iothread.
>> > + * Else, it's the main thread.
>> > + * These members can be safely accessed without locks.
>> > + */
>> > ReadLineState *rs;
>> > + // other members that aren't shared
>>
>> Whoops, misunderstanding! I meant this line as a placeholder, to
>> further illustrate my intent. It should not be committed. If we need a
>> comment here, it should use /* traditional comment syntax */.
>
> My fault.
>
> Please let me know if you want me to repost... Thanks,
Can touch that up, too. No respin needed unless something more complex
comes up.
next prev parent reply other threads:[~2018-05-24 11:16 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
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 [this message]
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=87bmd55mo4.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peterx@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).