From: Li Zhang <zhlcindy@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Li Zhang" <li.zhang@cloud.ionos.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>,
"Pankaj Gupta" <pankaj.gupta@ionos.com>
Subject: Re: [PATCHv2 1/1] Support monitor chardev hotswap with QMP
Date: Mon, 19 Apr 2021 13:56:43 +0200 [thread overview]
Message-ID: <CAD8of+q+3Ekv3SkCtQdoPMkjrh-8hAakCk3uV=WzDF_Y-A7uaA@mail.gmail.com> (raw)
In-Reply-To: <87blad2v9x.fsf@dusky.pond.sub.org>
On Sat, Apr 17, 2021 at 10:02 AM Markus Armbruster <armbru@redhat.com> wrote:
>
> Marc-André Lureau <marcandre.lureau@gmail.com> writes:
>
> > Hi
> >
> > On Fri, Apr 16, 2021 at 6:59 PM Marc-André Lureau <
> > marcandre.lureau@gmail.com> wrote:
> >
> >> Hi
> >>
> >> On Fri, Apr 16, 2021 at 6:51 PM Markus Armbruster <armbru@redhat.com>
> >> wrote:
> >>
> >>> Marc-André, I'd like your opinion for this one, in particular the use of
> >>> g_source_remove().
> >>>
> >>
> >> My opinion isn't really worth much, my review would have a bit more value.
> >>
> >> GSource has indeed some peculiar lifetime management, that I got wrong in
> >> the past. So I would be extra careful.
> >>
> >> But before spending time on review, I would also clarify the motivation
> >> and ask for testing.
> >>
> >> Markus, hot-adding/removing monitors isn't supported?
> >>
> >>
> > I realize you answered my question below. That's surprising me. Wouldn't it
> > make more sense to support it rather than having a pre-opened null-based
> > monitor that can have its chardev swapped?
>
> Yes, it would. Patches welcome.
>
> This patch is a somewhat ham-fisted and limited solution to the problem
> stated in the commit message. However, it might *also* be a reasonable
> improvement to chardev-change on its own. Not for me to judge.
>
Okay, Thanks.
> chardev-change comes with a number of restrictions. Let's have a closer
> look. It fails
>
> 1. when no such character device exists (d'oh)
>
> 2. for chardev-mux devices
>
> 3. in record/replay mode
>
> 4. when a backend is connected that doesn't implement the chr_be_change()
> method
>
> 5. when chr_be_change() fails
>
> 6. when creating the new chardev fails[*]
>
> Items 2, 3, 4 are restrictions. I figure 2 and 4 are simply not
> implemented, yet. I'm not sure about 3.
>
For item 3,
source code mentions "chardev cannot be changed in record/replay mode".
I never tried it yet. I am not quite sure why it couldn't be changed.
> Whether we want to accept patches lifting restrictions is up to the
> chardev maintainers.
>
> This patch lifts restriction 4 for QMP monitor backends. Its monitor
> part looks acceptable to me, but I dislike its code duplication. Before
> we spend time on cleaning that up (or on deciding to clean it up later),
> I'd like to hear the chardev mantainers' judgement, because that's about
> more serious matters than cleanliness.
>
> Do I make sense?
Yes, make sense. Thanks.
>
> [...]
>
>
> [*] The code for creating the new chardev in the "no backend connected"
> case
>
> be = chr->be;
> if (!be) {
> /* easy case */
> object_unparent(OBJECT(chr));
> return qmp_chardev_add(id, backend, errp);
> }
>
> is problematic: when qmp_chardev_add() fails, we already destroyed the
> old chardev. It should destroy the old chardev only when it can create
> its replacement.
>
You are right. It is a problem.
--
Best Regards
-Li
next prev parent reply other threads:[~2021-04-19 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 21:34 [PATCHv2 1/1] Support monitor chardev hotswap with QMP Li Zhang
2021-04-15 15:07 ` Li Zhang
2021-04-16 14:50 ` Markus Armbruster
2021-04-16 14:59 ` Marc-André Lureau
2021-04-16 15:28 ` Marc-André Lureau
2021-04-16 15:46 ` Li Zhang
2021-04-17 8:02 ` Markus Armbruster
2021-04-19 11:56 ` Li Zhang [this message]
2021-05-04 6:29 ` Pankaj Gupta
2021-05-04 8:38 ` Daniel P. Berrangé
2021-04-16 15:20 ` Li Zhang
2021-04-17 8:05 ` 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='CAD8of+q+3Ekv3SkCtQdoPMkjrh-8hAakCk3uV=WzDF_Y-A7uaA@mail.gmail.com' \
--to=zhlcindy@gmail.com \
--cc=armbru@redhat.com \
--cc=li.zhang@cloud.ionos.com \
--cc=marcandre.lureau@gmail.com \
--cc=pankaj.gupta@ionos.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).