| commit | 1a665855d7144bb3df382630a2b5e4039e95e466 | |
| author | Halil Pasic <pasic@linux.vnet.ibm.com> | |
| Thu, 6 Oct 2016 12:55:39 +0000 (6 14:55 +0200) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Sun, 9 Oct 2016 23:21:42 +0000 (10 02:21 +0300) | ||
| tree | 4ad59b83b37cc7a61a5a173eab5307a4418e8428 | treesnapshot (tar.gz zip) |
| parent | 0a73336d96397c80881219d080518fac6f1ecacb | commitdiff |
virtio: prepare change VMSTATE_VIRTIO_DEVICE macro
In most cases the functions passed to VMSTATE_VIRTIO_DEVICE
only call the virtio_load and virtio_save wrappers. Some include some
pre- and post- massaging too. The massaging is better expressed
as such in the VMStateDescription.
Let us prepare for changing the semantic of the VMSTATE_VIRTIO_DEVICE
macro so that it is more similar to the other VMSTATE_*_DEVICE macros
in a sense that it is a field definition.
The preprocessor conditionals are going to be removed as soon as
every usage is converted to the new semantic.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
In most cases the functions passed to VMSTATE_VIRTIO_DEVICE
only call the virtio_load and virtio_save wrappers. Some include some
pre- and post- massaging too. The massaging is better expressed
as such in the VMStateDescription.
Let us prepare for changing the semantic of the VMSTATE_VIRTIO_DEVICE
macro so that it is more similar to the other VMSTATE_*_DEVICE macros
in a sense that it is a field definition.
The preprocessor conditionals are going to be removed as soon as
every usage is converted to the new semantic.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| hw/virtio/virtio.c | diffblobblamehistory | |
| include/hw/virtio/virtio.h | diffblobblamehistory |