qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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
Date: Wed, 06 Oct 2010 14:02:19 -0500	[thread overview]
Message-ID: <4CACC7BB.3050401@codemonkey.ws> (raw)
In-Reply-To: <549264095.529061286324898345.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

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

  parent reply	other threads:[~2010-10-06 19:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1820922650.529041286324880996.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-10-06  0:28 ` [Qemu-devel] [PATCH 0/2] USB CCID device Alon Levy
2010-10-06  8:55   ` Gerd Hoffmann
2010-10-06 19:00     ` Anthony Liguori
2010-10-07  7:14       ` Gerd Hoffmann
2010-10-07  7:39       ` Alon Levy
2010-10-07 19:54         ` Anthony Liguori
2010-10-06 19:02   ` Anthony Liguori [this message]
2010-10-06 22:12     ` Alon Levy
2010-10-07 19:56       ` Anthony Liguori
     [not found] <668252848.649521286402747765.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-10-06 22:06 ` Alon Levy
2010-10-05 21:32 Alon Levy
2010-10-05 23:02 ` Anthony Liguori

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=4CACC7BB.3050401@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).