On 11/03/2016 12:14 PM, Halil Pasic wrote:
>
>
> On 11/02/2016 05:38 PM, Paolo Bonzini wrote:
>>
>>
>> On 02/11/2016 11:45, Juan Quintela wrote:
> +while (qemu_get_byte(f)) {
> +elm = g_malloc(size);
>>> I think this is not generic enough. We really need to allocate a new
>
On 11/02/2016 05:38 PM, Paolo Bonzini wrote:
>
>
> On 02/11/2016 11:45, Juan Quintela wrote:
+while (qemu_get_byte(f)) {
+elm = g_malloc(size);
>> I think this is not generic enough. We really need to allocate a new
>> element, and then fill it with default values.
>>
>>
On 11/02/2016 03:45 AM, Juan Quintela wrote:
> Jianjun Duan wrote:
>> Currently we cannot directly transfer a QTAILQ instance because of the
>> limitation in the migration code. Here we introduce an approach to
>> transfer such structures. We created VMStateInfo vmstate_info_qtailq
>> for QTAILQ
On 02/11/2016 11:45, Juan Quintela wrote:
>> > +while (qemu_get_byte(f)) {
>> > +elm = g_malloc(size);
> I think this is not generic enough. We really need to allocate a new
> element, and then fill it with default values.
>
> virtio list code use it in this way.
One thing at a tim
Jianjun Duan wrote:
> Currently we cannot directly transfer a QTAILQ instance because of the
> limitation in the migration code. Here we introduce an approach to
> transfer such structures. We created VMStateInfo vmstate_info_qtailq
> for QTAILQ. Similar VMStateInfo can be created for other data s
Currently we cannot directly transfer a QTAILQ instance because of the
limitation in the migration code. Here we introduce an approach to
transfer such structures. We created VMStateInfo vmstate_info_qtailq
for QTAILQ. Similar VMStateInfo can be created for other data structures
such as list.
This
