From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=54667 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P3ZFy-0001w7-Eg
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 15:02:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1P3ZFx-0008WE-35
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 15:02:26 -0400
Received: from mail-qy0-f173.google.com ([209.85.216.173]:34374)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1P3ZFw-0008WA-TG
	for qemu-devel@nongnu.org; Wed, 06 Oct 2010 15:02:25 -0400
Received: by qyk32 with SMTP id 32so3410027qyk.4
	for <qemu-devel@nongnu.org>; Wed, 06 Oct 2010 12:02:24 -0700 (PDT)
Message-ID: <4CACC7BB.3050401@codemonkey.ws>
Date: Wed, 06 Oct 2010 14:02:19 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/2] USB CCID device
References: <549264095.529061286324898345.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
In-Reply-To: <549264095.529061286324898345.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org

On 10/05/2010 07:28 PM, Alon Levy wrote:
> ----- "Anthony Liguori"<anthony@codemonkey.ws>  wrote:
>
>    
>> On 10/05/2010 04:32 PM, 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, so if the first reviewer can
>>>        
>> suggest
>>      
>>> a good way to split it I would gladly do that.
>>>
>>> Alon Levy (2):
>>>     usb-ccid: add CCID device. add configure option.
>>>     usb-ccid: add CCID device (device itself)
>>>
>>>        
>> Does this work with live migration?  I can't see how it would.
>>
>>      
> No, it doesn't right now. It would require cooperation with the client,
> to tell it to reconnect to the target qemu (kind of like spice).
>    

Is that because the device's logic is implemented in software outside of 
qemu or because it's somehow tied to hardware?

If it's the former, disconnect is not acceptable.  The logic for the 
software implementation should reside in qemu such that the device can 
be properly migrated.

If it's tied to hardware, it's just another form of device assignment 
and see my other mail.

Regards,

Anthony Liguori