From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] spice: add chardev
Date: Thu, 16 Dec 2010 18:48:59 +0200 [thread overview]
Message-ID: <20101216164859.GA27251@playa.tlv.redhat.com> (raw)
In-Reply-To: <4D0A124C.6080108@redhat.com>
On Thu, Dec 16, 2010 at 02:21:16PM +0100, Gerd Hoffmann wrote:
> On 12/16/10 12:29, Alon Levy wrote:
> >Adding a chardev backend for spice, for usage by spice vdagent in
> >conjunction with a properly named virtio-serial device.
>
> Usage example would be nice here.
>
> >+#ifdef CONFIG_SPICE
> >+#include "spice-qemu-char.h"
> >+#endif
>
> #ifdef can be dropped.
>
ok.
> >+#ifdef CONFIG_SPICE
> >+ {
> >+ .name = "name",
> >+ .type = QEMU_OPT_STRING,
> >+ },{
> >+ .name = "debug",
> >+ .type = QEMU_OPT_NUMBER,
> >+ },
> >+#endif
>
> This too.
ok.
>
> >@@ -1381,7 +1384,10 @@ Backend is one of:
> > @option{stdio},
> > @option{braille},
> > @option{tty},
> >-@option{parport}.
> >+@option{parport}
> >+#if defined(CONFIG_SPICE)
> >+@option{spicevmc}.
> >+#endif
>
> This too, documentation should be there unconditionally.
>
ok.
> >+//#define SPICE_QEMU_CHAR_USE_IOCTL
>
> Why is this disabled?
> Does it depend on the chardev patches from Amit?
>
There was a long discussion that concluded we don't want IOCTL's at all,
and that there should be some other mechanism for connection state
communication between the two sides. Meanwhile I found out I don't need
these (I don't remember exactly what I used instead, but basically just
the regular results of write/read).
> >diff --git a/spice-qemu-char.h b/spice-qemu-char.h
> >new file mode 100644
> >index 0000000..32d5009
> >--- /dev/null
> >+++ b/spice-qemu-char.h
> >@@ -0,0 +1,9 @@
> >+#ifndef __SPICE_QEMU_CHAR_H__
> >+#define __SPICE_QEMU_CHAR_H__
> >+
> >+#include "qemu-char.h"
> >+
> >+CharDriverState *qemu_chr_open_spice(QemuOpts *opts);
> >+
> >+#endif // __SPICE_QEMU_CHAR_H__
> >+
>
> Hmm, maybe add this to ui/qemu-spice.h instead, so we don't clutter
> the tree with lots of tiny includes?
ok.
>
> cheers,
> Gerd
next prev parent reply other threads:[~2010-12-16 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:29 [Qemu-devel] [PATCH 1/1] spice: add chardev Alon Levy
2010-12-16 13:21 ` Gerd Hoffmann
2010-12-16 16:48 ` Alon Levy [this message]
2010-12-16 16:53 ` Gerd Hoffmann
2010-12-17 12:54 ` Alon Levy
-- strict thread matches above, loose matches on Subject: below --
2010-11-30 14:29 [Qemu-devel] [PATCH 0/1] introduce spice-qemu-char chardev Alon Levy
2010-11-30 14:29 ` [Qemu-devel] [PATCH 1/1] spice: add chardev 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=20101216164859.GA27251@playa.tlv.redhat.com \
--to=alevy@redhat.com \
--cc=kraxel@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).