qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: Anthony Liguori <aliguori@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC adding ioctl's to virtserial/virtconsole
Date: Mon, 2 Aug 2010 14:33:39 +0530	[thread overview]
Message-ID: <20100802090339.GA4301@amit-laptop.redhat.com> (raw)
In-Reply-To: <1504146626.525061280738029828.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

On (Mon) Aug 02 2010 [04:33:49], 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.

Looks fine to me, maybe you don't need the notifications for
virtio-console ports, only the virtio-serial ports could be of interest,
but I'm fine with both notifying as well.

Also, this description could be made part of the patch description
itself.

		Amit

  reply	other threads:[~2010-08-02  9:03 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 [this message]
2010-08-02 15:04   ` Anthony Liguori
     [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=20100802090339.GA4301@amit-laptop.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=alevy@redhat.com \
    --cc=aliguori@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).