From: Kevin Wolf <kwolf@redhat.com>
To: Roman Penyaev <r.peniaev@gmail.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v4 6/8] chardev/char-mux: implement backend chardev multiplexing
Date: Fri, 17 Jan 2025 14:20:13 +0100 [thread overview]
Message-ID: <Z4pZDeGqoqg4Iedk@redhat.com> (raw)
In-Reply-To: <CACZ9PQVzRwgqix=6Do67kgLEJNP4xQZ4dHKrfONHh78vJU1CLg@mail.gmail.com>
Am 17.01.2025 um 09:03 hat Roman Penyaev geschrieben:
> On Thu, Jan 16, 2025 at 12:27 PM Kevin Wolf <kwolf@redhat.com> wrote:
> > Whatever you choose to do, my one request for you would be that you
> > really make sure that CLI and QMP are structured and behave exactly the
> > same with your new option, to avoid making the problem worse than it
> > already is.
>
> I understand this as keeping compatibility between CLI and QAPI at the
> command line interface level. In simple words: a new command line option
> "list.0=id0,list.1=id1" should be parsed in CLI exactly as QAPI will parse
> it in the possible bright future (I mean once the whole chardev is switched
> to QAPI). If my understanding is correct, then, with Markus and Mark-Andre
> help, I'm on the right track.
Yes, that's exactly what I mean. Good to hear that you're already
planning to keep this in mind.
Kevin
next prev parent reply other threads:[~2025-01-17 13:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 10:25 [PATCH v4 0/8] chardev: implement backend chardev multiplexing Roman Penyaev
2024-10-16 10:25 ` [PATCH v4 1/8] chardev/char: rename `MuxChardev` struct to `MuxFeChardev` Roman Penyaev
2024-10-16 10:25 ` [PATCH v4 2/8] chardev/char: rename `char-mux.c` to `char-mux-fe.c` Roman Penyaev
2024-10-16 10:26 ` [PATCH v4 3/8] chardev/char: move away mux suspend/resume calls Roman Penyaev
2024-10-16 10:26 ` [PATCH v4 4/8] chardev/char: rename frontend mux calls Roman Penyaev
2024-10-16 10:26 ` [PATCH v4 5/8] chardev/char: introduce `mux-be-id=ID` option Roman Penyaev
2024-10-16 10:26 ` [PATCH v4 6/8] chardev/char-mux: implement backend chardev multiplexing Roman Penyaev
2024-10-16 11:13 ` Marc-André Lureau
2024-10-16 11:18 ` Marc-André Lureau
2024-10-16 14:19 ` Roman Penyaev
2024-11-20 8:00 ` Roman Penyaev
2024-12-11 9:42 ` Markus Armbruster
2024-12-17 10:32 ` Roman Penyaev
2024-12-19 13:45 ` Markus Armbruster
2025-01-16 11:27 ` Kevin Wolf
2025-01-17 8:03 ` Roman Penyaev
2025-01-17 13:20 ` Kevin Wolf [this message]
2024-10-16 10:26 ` [PATCH v4 7/8] tests/unit/test-char: add unit test for the `mux-be` multiplexer Roman Penyaev
2024-10-16 11:36 ` Marc-André Lureau
2024-10-17 13:48 ` Roman Penyaev
2024-10-16 10:26 ` [PATCH v4 8/8] qemu-options.hx: describe multiplexing of several backend devices Roman Penyaev
2024-10-16 11:27 ` 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=Z4pZDeGqoqg4Iedk@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=r.peniaev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.