From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: postpone monitor_qmp_cleanup_queues
Date: Fri, 8 Jun 2018 17:24:57 +0800 [thread overview]
Message-ID: <20180608092457.GG7736@xz-mi> (raw)
In-Reply-To: <20180608091154.GF7736@xz-mi>
On Fri, Jun 08, 2018 at 05:11:54PM +0800, Peter Xu wrote:
[...]
> Frankly speaking I think this might be an ideal fix as well. For
> example what if we are executing the dispatcher of a command when we
> received the CLOSED event? If so, the dispatcher will put the
> response onto the response queue after the CLOSED event, and ideally
> we'd better also deliver that to the filter_output process.
Please ignore this paragraph. Actually if that happens, we'll queue
the response onto the response queue as usual, then as long as the
output channel is not closed it'll still be delivered to the
filter_output process.
So I think I agree with Markus's solution, we just flush the response
queue when we get CLOSED (but we don't close the output fd; IMHO
that's chardev backend's job). Would that work?
Regards,
--
Peter Xu
next prev parent reply other threads:[~2018-06-08 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 8:06 [Qemu-devel] [PATCH] monitor: postpone monitor_qmp_cleanup_queues Peter Xu
2018-06-04 15:01 ` Marc-André Lureau
2018-06-05 3:39 ` Peter Xu
2018-06-07 11:53 ` Markus Armbruster
2018-06-08 4:42 ` Peter Xu
2018-06-08 7:05 ` Markus Armbruster
2018-06-08 8:04 ` Stefan Hajnoczi
2018-06-08 8:18 ` Markus Armbruster
2018-06-08 9:11 ` Peter Xu
2018-06-08 9:24 ` Peter Xu [this message]
2018-06-11 7:58 ` Markus Armbruster
2018-06-11 16:45 ` Stefan Hajnoczi
2018-06-12 5:47 ` Peter Xu
2018-06-13 14:30 ` Stefan Hajnoczi
2018-06-14 3:05 ` 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=20180608092457.GG7736@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).