|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [PATCH 0/2] USB CCID device |
Date: | Thu, 07 Oct 2010 14:56:02 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8 |
On 10/06/2010 05:12 PM, Alon Levy wrote:
Actually, both are possible - but the later is the interesting use case (the former is mainly for debugging). To elaborate: the device is meant to allow a hardware reader to be available to the guest while still being available to the client (which is running on the computer with the real reader attached). So the real card is what we are talking to. The other usage is to have a virtual card, which would actually be more logical to put with the qemu device, but It isn't my current focus (the focus being the real card, and the virtual card being implemented in the client side is a testing measure).
Okay, that makes sense.
I'll do this. A side note: I tried migrating a QSIMPLEQ today - not a fun experience. I'm wondering if this is a result of a mentality that "all devices should allocate memory upfront" that makes using / migrating dynamic linked lists a non-starter, or just an oversight (no one wrote VMSTATE_QSIMPLEQ yet). As it stands migrating a QSIMPLEQ (or any other list) is much easier the old way without using VMSTATE. </rant>.
Yeah, complex types are not at all easy to migrate today. Something we need to tackle with vmstate2 eventually.
Regards, Anthony Liguori
Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |