From: Gerd Hoffmann <kraxel@redhat.com>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 9/9] chardev: add hotplug support.
Date: Wed, 17 Oct 2012 11:27:25 +0200 [thread overview]
Message-ID: <507E79FD.1060304@redhat.com> (raw)
In-Reply-To: <507D2543.2090306@linux.vnet.ibm.com>
Hi,
>> +- "id": the chardev's ID, must be unique (json-string)
>> +- "backend": the chardev backend: "file", "socket", ... (json-string)
>> +- "path": file / device / unix socket path (json-string, optional)
>> +- "name": spice channel name (json-string, optional)
>> +- "host": host name (json-string, optional)
>> +- "port": port number (json-string, optional)
>> +- "server": create socket in server mode (json-bool, optional)
>> +- "wait": wait for connect (json-bool, optional)
>> +- "ipv4": force ipv4-only (json-bool, optional)
>> +- "ipv6": force ipv6-only (json-bool, optional)
>> +- "telnet": telnet negotiation (json-bool, optional)
>> +
>
> As mentioned in another thread, should it support the "mux" argument
> for multiplexing mode?
I don't think so. Basically the only use case for the mux chardev is
-nographic with serial line + monitor being multiplexed on stdio.
cheers,
Gerd
next prev parent reply other threads:[~2012-10-17 9:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:06 [Qemu-devel] [PATCH v3 0/9] serial device hotplug patch series Gerd Hoffmann
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 1/9] serial: split serial.c Gerd Hoffmann
2012-10-15 14:16 ` Anthony Liguori
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 2/9] serial: add pci variant Gerd Hoffmann
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 3/9] serial: add windows inf file for the pci card to docs Gerd Hoffmann
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 4/9] serial: add 2x + 4x pci variant Gerd Hoffmann
2012-10-15 14:18 ` Anthony Liguori
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 5/9] usb-serial: don't magically zap chardev on umplug Gerd Hoffmann
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 6/9] usb-serial: only expose device in guest when the chardev is open Gerd Hoffmann
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 7/9] chardev: add error reporting for qemu_chr_new_from_opts Gerd Hoffmann
2012-10-17 1:12 ` Luiz Capitulino
2012-10-17 1:13 ` Luiz Capitulino
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 8/9] chardev: fix QemuOpts lifecycle Gerd Hoffmann
2012-10-17 1:18 ` Luiz Capitulino
2012-10-15 8:06 ` [Qemu-devel] [PATCH v3 9/9] chardev: add hotplug support Gerd Hoffmann
2012-10-15 14:22 ` Anthony Liguori
2012-10-15 18:04 ` Eric Blake
2012-10-17 1:49 ` Luiz Capitulino
2012-10-16 9:13 ` Lei Li
2012-10-17 9:27 ` Gerd Hoffmann [this message]
2012-10-17 1:28 ` Luiz Capitulino
2012-10-17 1:52 ` [Qemu-devel] [PATCH v3 0/9] serial device hotplug patch series Luiz Capitulino
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=507E79FD.1060304@redhat.com \
--to=kraxel@redhat.com \
--cc=lilei@linux.vnet.ibm.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).