From: Peter Xu <peterx@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/6] monitor: accept chardev input from iothread
Date: Wed, 10 Oct 2018 11:45:25 +0800 [thread overview]
Message-ID: <20181010034525.GM18728@xz-x1> (raw)
In-Reply-To: <20181009131251.721-3-marcandre.lureau@redhat.com>
On Tue, Oct 09, 2018 at 05:12:47PM +0400, Marc-André Lureau wrote:
> Chardev backends may not handle safely IO events from concurrent
> threads. Better to wake up the chardev from the monitor IO thread if
> it's being used as the chardev context.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> monitor.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index ab60c9f87e..a25514490a 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -4297,6 +4297,13 @@ int monitor_suspend(Monitor *mon)
> return 0;
> }
>
> +static void monitor_accept_input(void *opaque)
> +{
> + Monitor *mon = opaque;
> +
> + qemu_chr_fe_accept_input(&mon->chr);
> +}
> +
> void monitor_resume(Monitor *mon)
> {
> if (monitor_is_hmp_non_interactive(mon)) {
> @@ -4310,13 +4317,14 @@ void monitor_resume(Monitor *mon)
> * let's kick the thread in case it's sleeping.
> */
> if (mon->use_io_thread) {
> - aio_notify(iothread_get_aio_context(mon_iothread));
> + aio_bh_schedule_oneshot(iothread_get_aio_context(mon_iothread),
> + monitor_accept_input, mon);
Just to make sure: this will definitely cover the previous
aio_notify(), am I right?
Imho some comment would always be nice here because QMPs with
use_io_thread=true seems special anyway.
> }
> } else {
> assert(mon->rs);
> readline_show_prompt(mon->rs);
> + monitor_accept_input(mon);
> }
> - qemu_chr_fe_accept_input(&mon->chr);
How about the QMP monitors with oob=off? Will it miss the call?
I would consider caching the aio context into Monitor struct when
monitor init, then call aio_bh_schedule_oneshot() always with the
per-monitor aio cache. This could unify the code paths too so we keep
the oob special path as less as possible.
> }
> trace_monitor_suspend(mon, -1);
> }
> --
> 2.19.0.271.gfe8321ec05
>
Regards,
--
Peter Xu
next prev parent reply other threads:[~2018-10-10 3:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:12 [Qemu-devel] [PATCH 0/6] monitor: misc fixes Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 1/6] monitor: inline ambiguous helper functions Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 2/6] monitor: accept chardev input from iothread Marc-André Lureau
2018-10-10 3:45 ` Peter Xu [this message]
2018-10-29 11:34 ` Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag Marc-André Lureau
2018-10-10 3:54 ` Peter Xu
2018-10-29 11:45 ` Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 4/6] monitor: check if chardev can switch gcontext for OOB Marc-André Lureau
2018-10-10 4:37 ` Peter Xu
2018-10-29 12:06 ` Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 5/6] monitor: prevent inserting new monitors after cleanup Marc-André Lureau
2018-10-09 13:12 ` [Qemu-devel] [PATCH 6/6] monitor: avoid potential dead-lock when cleaning up Marc-André Lureau
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=20181010034525.GM18728@xz-x1 \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).