[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support t
From: |
Andreas Färber |
Subject: |
Re: [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support to VirtIODevice |
Date: |
Mon, 19 May 2014 19:06:39 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 |
Am 19.05.2014 15:06, schrieb Greg Kurz:
> On Mon, 19 May 2014 10:39:09 +0200
> Greg Kurz <address@hidden> wrote:
>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>> index 7fbad29..6578854 100644
>> --- a/hw/virtio/virtio.c
>> +++ b/hw/virtio/virtio.c
[...]
>> @@ -839,10 +849,39 @@ typedef struct VirtIOSubsection {
>> int version_id;
>> void (*save)(VirtIODevice *vdev, QEMUFile *f);
>> int (*load)(VirtIODevice *vdev, QEMUFile *f);
>> - int (*needed)(VirtIODevice *vdev);
>> + bool (*needed)(VirtIODevice *vdev);
>> } VirtIOSubsection;
>>
>> +static void virtio_save_device_endian(VirtIODevice *vdev, QEMUFile *f)
>> +{
>> + qemu_put_byte(f, vdev->device_endian);
>> +}
>> +
>> +static int virtio_load_device_endian(VirtIODevice *vdev, QEMUFile *f)
>> +{
>> + vdev->device_endian = qemu_get_byte(f);
>> + return 0;
>> +}
>> +
>> +static bool virtio_device_endian_needed(VirtIODevice *vdev)
>> +{
>> + /* No migration is supposed to occur while we are loading state.
>> + */
>> + assert(vdev->device_endian != VIRTIO_DEVICE_ENDIAN_UNKNOWN);
>> + if (target_words_bigendian()) {
>> + return vdev->device_endian == VIRTIO_DEVICE_ENDIAN_LITTLE;
>> + } else {
>> + return vdev->device_endian == VIRTIO_DEVICE_ENDIAN_BIG;
>> + }
>> +}
>> +
>> static const VirtIOSubsection virtio_subsection[] = {
>> + { .name = "virtio/device_endian",
>
> Can anyone comment the subsection name ? Is there a chance the
> VMState port would come up with the same ?
>
>> + .version_id = 1,
>> + .save = virtio_save_device_endian,
>> + .load = virtio_load_device_endian,
>> + .needed = virtio_device_endian_needed,
>> + },
>> { .name = NULL }
>> };
>>
Different question: With converting VirtIO to VMState in mind, why are
you not using a regular VMStateSubsection and loading/saving that as
part of the old-style load/save functions? Is an API for that missing?
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
- [Qemu-devel] [PATCH RFC V2 0/8] virtio: migrate new properties, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 1/8] virtio: introduce device specific migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 2/8] virtio-net: implement per-device migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 3/8] virtio-blk: implement per-device migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 4/8] virtio-serial: implement per-device migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 5/8] virtio-balloon: implement per-device migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 6/8] virtio-rng: implement per-device migration calls, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 7/8] virtio: add subsections to the migration stream, Greg Kurz, 2014/05/19
- [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support to VirtIODevice, Greg Kurz, 2014/05/19
- Re: [Qemu-devel] [PATCH RFC V2 0/8] virtio: migrate new properties, Alexander Graf, 2014/05/19