From: Roman Penyaev <r.peniaev@gmail.com>
Cc: "Roman Penyaev" <r.peniaev@gmail.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: [PATCH 0/2] chardev: implement backend chardev multiplexing
Date: Fri, 13 Sep 2024 18:36:34 +0200 [thread overview]
Message-ID: <20240913163636.253949-1-r.peniaev@gmail.com> (raw)
Mux is a character backend (host side) device, which multiplexes
multiple frontends with one backend device. The following is a
few lines from the QEMU manpage [1]:
A multiplexer is a "1:N" device, and here the "1" end is your
specified chardev backend, and the "N" end is the various parts
of QEMU that can talk to a chardev.
But sadly multiple backends are not supported.
This work implements multiplexing capability of several backend
devices, which opens up an opportunity to use a single frontend
device on the guest, which can be manipulated from several
backend devices.
The main motivation of this work is to use a virtio console
frontend device on the guest, which can be manipulated from
several backend devices. The following is QEMU command line
example:
-chardev socket,path=/tmp/sock,server=on,wait=off,id=sock0 \
-chardev vc,id=vc0 \
-chardev mux,id=mux0,chardev=vc0,,sock0 \
-device virtconsole,chardev=mux0 \
-vnc 0.0.0.0:0
Which creates 2 backend devices: text virtual console (`vc0`)
and a socket (`sock0`) connected to the single virtio hvc
console with the multiplexer (`mux0`) help. `vc0` renders
text to an image, which can be shared over the VNC protocol.
`sock0` is a socket backend which provides biderectional
communication to the virtio hvc console.
Once QEMU starts VNC client and any TTY emulator can be used to
control a single hvc console, for example these two different
consoles should have similar input and output due the buffer
multiplexing:
# VNC client
vncviewer :0
# TTY emulator
socat unix:connect:/tmp/sock pty,link=/tmp/pty
tio /tmp/pty
[1] https://www.qemu.org/docs/master/system/qemu-manpage.html#hxtool-6
Roman Penyaev (2):
chardev: implement backend chardev multiplexing
qemu-options.hx: describe multiplexing of several backend devices
chardev/char-fe.c | 14 +++--
chardev/char-mux.c | 120 +++++++++++++++++++++++++++++--------
chardev/char.c | 2 +-
chardev/chardev-internal.h | 7 ++-
qemu-options.hx | 44 ++++++++++++--
5 files changed, 151 insertions(+), 36 deletions(-)
Signed-off-by: Roman Penyaev <r.peniaev@gmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
--
2.34.1
next reply other threads:[~2024-09-13 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 16:36 Roman Penyaev [this message]
2024-09-13 16:36 ` [PATCH 1/2] chardev: implement backend chardev multiplexing Roman Penyaev
2024-09-17 12:31 ` Marc-André Lureau
2024-09-17 12:40 ` Peter Maydell
2024-09-17 12:56 ` Peter Maydell
2024-09-17 14:15 ` Roman Penyaev
2024-09-18 10:52 ` Marc-André Lureau
2024-09-18 12:31 ` Roman Penyaev
2024-09-13 16:36 ` [PATCH 2/2] qemu-options.hx: describe multiplexing of several backend devices Roman Penyaev
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=20240913163636.253949-1-r.peniaev@gmail.com \
--to=r.peniaev@gmail.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).