From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: "Armbruster, Markus" <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Bonzini, Paolo" <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/6] monitor: check if chardev can switch gcontext for OOB
Date: Mon, 3 Dec 2018 12:44:27 +0400 [thread overview]
Message-ID: <CAMxuvay4ODSSTivjnQ=Fs2iDZujScU9hQkPxLfTCAEADf1m-Rw@mail.gmail.com> (raw)
In-Reply-To: <871s6z81da.fsf@dusky.pond.sub.org>
Hi
On Mon, Dec 3, 2018 at 12:23 PM Markus Armbruster <armbru@redhat.com> wrote:
>
> Marc-André Lureau <marcandre.lureau@redhat.com> writes:
>
> > Not all backends are able to switch gcontext. Those backends cannot
> > drive a OOB monitor (the monitor would then be blocking on main
> > thread).
> >
> > For example, ringbuf, spice, or more esoteric input chardevs like
> > braille or MUX.
> >
> > We currently forbid MUX because not all frontends are ready to run
> > outside main loop. Extend to add a context-switching feature check.
>
> Double-checking: the reason for forbidding MUX and the reason for
> requiring QEMU_CHAR_FEATURE_GCONTEXT are orthogonal, right?
Yes, to me the mux check is there because other front-end sides (other
than QMP monitor) may not handle dispatch from other threads.
Otoh, the GCONTEXT feature check is there to check if the chardev
(backend) handles switching context.
> > Note: this patch will conflict with Peter "[PATCH v9 3/6] monitor:
> > remove "x-oob", turn oob on by default", but can be trivially updated.
>
> I intend to merge this series first, and drop this sentence.
>
> > Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > ---
> > monitor.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/monitor.c b/monitor.c
> > index 511dd11d1c..fffeb27ef9 100644
> > --- a/monitor.c
> > +++ b/monitor.c
> > @@ -4560,9 +4560,11 @@ void monitor_init(Chardev *chr, int flags)
> > bool use_oob = flags & MONITOR_USE_OOB;
> >
> > if (use_oob) {
> > - if (CHARDEV_IS_MUX(chr)) {
> > + if (CHARDEV_IS_MUX(chr) ||
> > + !qemu_chr_has_feature(chr, QEMU_CHAR_FEATURE_GCONTEXT)) {
> > error_report("Monitor out-of-band is not supported with "
> > - "MUX typed chardev backend");
> > + "%s typed chardev backend",
> > + object_get_typename(OBJECT(chr)));
> > exit(1);
> > }
> > if (use_readline) {
>
next prev parent reply other threads:[~2018-12-03 8:44 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
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 [this message]
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='CAMxuvay4ODSSTivjnQ=Fs2iDZujScU9hQkPxLfTCAEADf1m-Rw@mail.gmail.com' \
--to=marcandre.lureau@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).