From: Anthony Liguori <anthony@codemonkey.ws>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] usb-ccid device (v2)
Date: Tue, 12 Oct 2010 08:24:45 -0500 [thread overview]
Message-ID: <4CB4619D.1010101@codemonkey.ws> (raw)
In-Reply-To: <1286888309-4493-1-git-send-email-alevy@redhat.com>
On 10/12/2010 07:58 AM, Alon Levy wrote:
> This patch adds a new device, it is described in full in the second patch
> intro and also in the documentation in docs. In brief it provides a standard
> smart card reader device.
>
> The first patch is the configure change and docs.
> The second patch contains the actual device, I couldn't figure out a good
> way to split it to ease review.
>
> v2 changed:
> * all QSIMPLEQ turned into fixed sized rings
> * all allocated buffers turned into fixed size buffers
> * added migration support
> * added a message to tell client qemu has migrated to ip:port
> * for lack of monitor commands ip:port are 0:0, which causes the updated
> vscclient to connect to one port higher on the same host. will add monitor
> commands in a separate patch. tested with current setup.
>
This is way too much magic to live within a device. Devices manage
reconnecting themselves during migration. When you create the
destination qemu instance, you specify what to connect to.
IOW,
On the source:
qemu -chardev tcp:localhost:1025,id=foo -usbdevice ccid,chardev=foo ...
On the destination:
qemu -chardev tcp:localhost:1026,id=foo -usbdevice ccid,chardev=foo
-incoming tcp:0.0.0.0:1024 ...
A connection happens when the device is created.
But now I'm even further confused then when I first reviewed it.. If
you're now supporting migration, does that mean that you're relying on
the daemon to emulate the device?
Regards,
Anthony Liguori
> Alon Levy (2):
> usb-ccid: add CCID device. add configure option.
> usb-ccid: add CCID device (device itself)
>
> Makefile.objs | 1 +
> configure | 12 +
> docs/usb-ccid.txt | 115 +++++
> hw/usb-ccid.c | 1376 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/vscard_common.h | 131 +++++
> 5 files changed, 1635 insertions(+), 0 deletions(-)
> create mode 100644 docs/usb-ccid.txt
> create mode 100644 hw/usb-ccid.c
> create mode 100644 hw/vscard_common.h
>
>
next prev parent reply other threads:[~2010-10-12 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 12:58 [Qemu-devel] [PATCH 0/2] usb-ccid device (v2) Alon Levy
2010-10-12 12:58 ` [Qemu-devel] [PATCH 1/2] usb-ccid: add CCID device. add configure option Alon Levy
2010-10-12 12:58 ` [Qemu-devel] [PATCH 2/2] usb-ccid: add CCID device (device itself) Alon Levy
2010-10-12 13:24 ` Anthony Liguori [this message]
[not found] <1045788737.212361286898758903.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-10-12 16:03 ` [Qemu-devel] [PATCH 0/2] usb-ccid device (v2) Alon Levy
2010-10-12 16:21 ` Anthony Liguori
[not found] <593949580.216281286900989465.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-10-12 16:43 ` Alon Levy
2010-10-12 16:49 ` Anthony Liguori
2010-10-12 17:09 ` Alon Levy
2010-10-12 18:23 ` Anthony Liguori
2010-10-13 11:54 ` Alon Levy
-- strict thread matches above, loose matches on Subject: below --
2010-10-14 18:37 Robert Relyea
2010-10-14 18:52 ` Anthony Liguori
2010-10-14 22:03 ` Robert Relyea
2010-10-14 22:16 ` Anthony Liguori
2010-10-15 0:16 ` Robert Relyea
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=4CB4619D.1010101@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@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).