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 v2 2/6] monitor: accept chardev input from iothread
Date: Tue, 30 Oct 2018 11:43:03 +0800 [thread overview]
Message-ID: <20181030034303.GC22523@xz-x1> (raw)
In-Reply-To: <20181029125733.14597-3-marcandre.lureau@redhat.com>
On Mon, Oct 29, 2018 at 04:57:29PM +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.
>
> Unify code paths by using a BH in all cases.
>
> Drop the now redundant aio_notify() call.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> monitor.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index 07712d89f9..511dd11d1c 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -4304,6 +4304,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)) {
> @@ -4311,20 +4318,24 @@ void monitor_resume(Monitor *mon)
> }
>
> if (atomic_dec_fetch(&mon->suspend_cnt) == 0) {
> + AioContext *ctx = qemu_get_aio_context();
> +
> if (monitor_is_qmp(mon)) {
> /*
> * For QMP monitors that are running in the I/O thread,
> * let's kick the thread in case it's sleeping.
This comment seems stall, you may consider to touch it up, otherwise
it looks sane to me:
Reviewed-by: Peter Xu <peterx@redhat.com>
> */
> if (mon->use_io_thread) {
> - aio_notify(iothread_get_aio_context(mon_iothread));
> + ctx = iothread_get_aio_context(mon_iothread);
> }
> } else {
> assert(mon->rs);
> readline_show_prompt(mon->rs);
> }
> - qemu_chr_fe_accept_input(&mon->chr);
> +
> + aio_bh_schedule_oneshot(ctx, monitor_accept_input, mon);
> }
> +
> trace_monitor_suspend(mon, -1);
> }
>
> --
> 2.19.0.271.gfe8321ec05
>
Regards,
--
Peter Xu
next prev parent reply other threads:[~2018-10-30 3:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 12:57 [Qemu-devel] [PATCH v2 0/6] monitor: misc fixes Marc-André Lureau
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 1/6] monitor: inline ambiguous helper functions Marc-André Lureau
2018-10-30 3:33 ` Peter Xu
2018-12-03 6:58 ` Markus Armbruster
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 2/6] monitor: accept chardev input from iothread Marc-André Lureau
2018-10-30 3:43 ` Peter Xu [this message]
2018-12-03 7:10 ` Markus Armbruster
2018-12-03 8:04 ` Marc-André Lureau
2018-12-03 9:29 ` Markus Armbruster
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag Marc-André Lureau
2018-12-03 7:20 ` Markus Armbruster
2018-12-03 8:11 ` Marc-André Lureau
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 4/6] monitor: check if chardev can switch gcontext for OOB Marc-André Lureau
2018-12-03 8:23 ` Markus Armbruster
2018-12-03 8:44 ` Marc-André Lureau
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 5/6] monitor: prevent inserting new monitors after cleanup Marc-André Lureau
2018-10-30 5:42 ` Peter Xu
2018-12-03 8:59 ` Markus Armbruster
2018-12-03 9:55 ` Marc-André Lureau
2018-12-03 12:16 ` Markus Armbruster
2018-10-29 12:57 ` [Qemu-devel] [PATCH v2 6/6] monitor: avoid potential dead-lock when cleaning up Marc-André Lureau
2018-12-03 9:26 ` Markus Armbruster
2018-12-03 10:02 ` Marc-André Lureau
2018-12-03 12:17 ` Markus Armbruster
2018-10-30 5:48 ` [Qemu-devel] [PATCH v2 0/6] monitor: misc fixes Peter Xu
2018-10-30 8:06 ` Marc-André Lureau
2018-10-30 17:56 ` Markus Armbruster
2018-12-03 9:36 ` Markus Armbruster
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=20181030034303.GC22523@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).