From: Anthony Liguori <anthony@codemonkey.ws>
To: Alon Levy <alevy@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
Anthony Liguori <aliguori@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC adding ioctl's to virtserial/virtconsole
Date: Mon, 02 Aug 2010 10:04:43 -0500 [thread overview]
Message-ID: <4C56DE8B.5090302@codemonkey.ws> (raw)
In-Reply-To: <1504146626.525061280738029828.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
On 08/02/2010 03:33 AM, Alon Levy wrote:
> Hi,
>
> This patch adds three CHR_IOCTLs and uses them in virtserial devices, to be used
> by a chardev backend, such as a spice vm channel (spice is a vdi solution).
>
> Basically virtio-serial provides three driver initiated events for guest open of
> a device, guest close, and guest ready (driver port init complete) that before this
> patch are not exposed to the chardev backend.
>
> With the spicevmc backend this is used like this:
> qemu -chardev spicevmc,id=vdiport,name=vdiport -device virtserialport,chardev=vdiport,name=com.redhat.spice.0
>
> I'd appreciate any feedback if this seems the right way to accomplish this, and
> for the numbers I grabbed.
>
I really hate to add connection semantics via IOCTLs. I would rather we
add them as first class semantics to the char device layer. This would
allow us to use char devices for VNC, for instance.
Regards,
Anthony Liguori
> Alon
>
> -------------- commit message --------------------------------
> From a90d4e26df727ed0d2b64b705e955f695289fa61 Mon Sep 17 00:00:00 2001
> From: Alon Levy<alevy@redhat.com>
> Date: Mon, 2 Aug 2010 11:22:58 +0300
> Subject: [PATCH] virtio-console: add IOCTL's for guest_{ready,open,close}
>
> Add three IOCTL corresponding to the three control events of:
> guest_ready -> CHR_IOCTL_VIRT_SERIAL_READY
> guest_open -> CHR_IOCTL_VIRT_SERIAL_OPEN
> guest_close -> CHR_IOCTL_VIRT_SERIAL_CLOSE
>
> Can be used by a matching backend.
> ---
> hw/virtio-console.c | 33 +++++++++++++++++++++++++++++++++
> qemu-char.h | 4 ++++
> 2 files changed, 37 insertions(+), 0 deletions(-)
>
> diff --git a/hw/virtio-console.c b/hw/virtio-console.c
> index caea11f..4c3686d 100644
> --- a/hw/virtio-console.c
> +++ b/hw/virtio-console.c
> @@ -58,6 +58,33 @@ static void chr_event(void *opaque, int event)
> }
> }
>
> +static void virtconsole_guest_open(VirtIOSerialPort *port)
> +{
> + VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
> +
> + if (vcon->chr) {
> + qemu_chr_ioctl(vcon->chr, CHR_IOCTL_VIRT_SERIAL_OPEN, NULL);
> + }
> +}
> +
> +static void virtconsole_guest_close(VirtIOSerialPort *port)
> +{
> + VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
> +
> + if (vcon->chr) {
> + qemu_chr_ioctl(vcon->chr, CHR_IOCTL_VIRT_SERIAL_CLOSE, NULL);
> + }
> +}
> +
> +static void virtconsole_guest_ready(VirtIOSerialPort *port)
> +{
> + VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port);
> +
> + if (vcon->chr) {
> + qemu_chr_ioctl(vcon->chr, CHR_IOCTL_VIRT_SERIAL_READY, NULL);
> + }
> +}
> +
> /* Virtio Console Ports */
> static int virtconsole_initfn(VirtIOSerialDevice *dev)
> {
> @@ -94,6 +121,9 @@ static VirtIOSerialPortInfo virtconsole_info = {
> .qdev.size = sizeof(VirtConsole),
> .init = virtconsole_initfn,
> .exit = virtconsole_exitfn,
> + .guest_open = virtconsole_guest_open,
> + .guest_close = virtconsole_guest_close,
> + .guest_ready = virtconsole_guest_ready,
> .qdev.props = (Property[]) {
> DEFINE_PROP_UINT8("is_console", VirtConsole, port.is_console, 1),
> DEFINE_PROP_UINT32("nr", VirtConsole, port.id, VIRTIO_CONSOLE_BAD_ID),
> @@ -130,6 +160,9 @@ static VirtIOSerialPortInfo virtserialport_info = {
> .qdev.size = sizeof(VirtConsole),
> .init = virtserialport_initfn,
> .exit = virtconsole_exitfn,
> + .guest_open = virtconsole_guest_open,
> + .guest_close = virtconsole_guest_close,
> + .guest_ready = virtconsole_guest_ready,
> .qdev.props = (Property[]) {
> DEFINE_PROP_UINT32("nr", VirtConsole, port.id, VIRTIO_CONSOLE_BAD_ID),
> DEFINE_PROP_CHR("chardev", VirtConsole, chr),
> diff --git a/qemu-char.h b/qemu-char.h
> index e3a0783..1df53ae 100644
> --- a/qemu-char.h
> +++ b/qemu-char.h
> @@ -41,6 +41,10 @@ typedef struct {
> #define CHR_IOCTL_SERIAL_SET_TIOCM 13
> #define CHR_IOCTL_SERIAL_GET_TIOCM 14
>
> +#define CHR_IOCTL_VIRT_SERIAL_OPEN 15
> +#define CHR_IOCTL_VIRT_SERIAL_CLOSE 16
> +#define CHR_IOCTL_VIRT_SERIAL_READY 17
> +
> #define CHR_TIOCM_CTS 0x020
> #define CHR_TIOCM_CAR 0x040
> #define CHR_TIOCM_DSR 0x100
>
next prev parent reply other threads:[~2010-08-02 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2092558519.524651280737489312.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-02 8:33 ` [Qemu-devel] RFC adding ioctl's to virtserial/virtconsole Alon Levy
2010-08-02 9:03 ` Amit Shah
2010-08-02 15:04 ` Anthony Liguori [this message]
[not found] <183307416.602861280770002326.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-02 17:28 ` Alon Levy
2010-08-02 17:42 ` Anthony Liguori
2010-08-03 8:46 ` Gerd Hoffmann
2010-08-03 13:12 ` Anthony Liguori
2010-08-03 15:28 ` Gerd Hoffmann
2010-08-03 15:46 ` Anthony Liguori
2010-08-03 16:42 ` Gerd Hoffmann
2010-08-03 16:45 ` Anthony Liguori
2010-08-03 17:02 ` Gerd Hoffmann
2010-08-03 17:53 ` Anthony Liguori
2010-08-03 20:41 ` Gerd Hoffmann
2010-08-03 20:45 ` Anthony Liguori
[not found] <391834624.690531280844685997.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-03 14:13 ` Alon Levy
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=4C56DE8B.5090302@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=aliguori@redhat.com \
--cc=amit.shah@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).