Michael Roth a678e26cbe qapi: pad GenericList value fields to 64 bits ... With the introduction of native list types, we now have types such as int64List where the 'value' field is not a pointer, but the actual 64-bit value. On 32-bit architectures, this can lead to situations where 'next' field offset in GenericList does not correspond to the 'next' field in the types that we cast to GenericList when using the visit_next_list() interface, causing issues when we attempt to traverse linked list structures of these types. To fix this, pad the 'value' field of GenericList and other schema-defined/native *List types out to 64-bits. This is less memory-efficient for 32-bit architectures, but allows us to continue to rely on list-handling interfaces that target GenericList to simply visitor implementations. In the future we can improve efficiency by defaulting to using native C array backends to handle list of non-pointer types, which would be more memory efficient in itself and allow us to roll back this change. Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>		2013-05-30 09:08:38 -04:00
..
qmp	remove some double-includes	2013-05-18 16:35:12 +04:00
dealloc-visitor.h
error.h	misc: move include files to include/qemu/	2012-12-19 08:32:39 +01:00
opts-visitor.h	misc: move include files to include/qemu/	2012-12-19 08:32:39 +01:00
qmp-input-visitor.h
qmp-output-visitor.h
string-input-visitor.h
string-output-visitor.h
visitor-impl.h
visitor.h	qapi: pad GenericList value fields to 64 bits	2013-05-30 09:08:38 -04:00