From: "Andreas Färber" <afaerber@suse.de>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support to VirtIODevice
Date: Mon, 19 May 2014 19:06:39 +0200 [thread overview]
Message-ID: <537A3A1F.8010303@suse.de> (raw)
In-Reply-To: <20140519150633.4871817d@bahia.local>
Am 19.05.2014 15:06, schrieb Greg Kurz:
> On Mon, 19 May 2014 10:39:09 +0200
> Greg Kurz <gkurz@linux.vnet.ibm.com> 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
next prev parent reply other threads:[~2014-05-19 17:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 8:38 [Qemu-devel] [PATCH RFC V2 0/8] virtio: migrate new properties Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 1/8] virtio: introduce device specific migration calls Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 2/8] virtio-net: implement per-device " Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 3/8] virtio-blk: " Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 4/8] virtio-serial: " Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 5/8] virtio-balloon: " Greg Kurz
2014-05-19 8:38 ` [Qemu-devel] [PATCH RFC 6/8] virtio-rng: " Greg Kurz
2014-05-19 8:39 ` [Qemu-devel] [PATCH RFC 7/8] virtio: add subsections to the migration stream Greg Kurz
2014-05-19 8:39 ` [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support to VirtIODevice Greg Kurz
2014-05-19 13:06 ` Greg Kurz
2014-05-19 17:06 ` Andreas Färber [this message]
2014-05-19 17:32 ` Greg Kurz
2014-05-19 18:07 ` Dr. David Alan Gilbert
2014-05-19 12:02 ` [Qemu-devel] [PATCH RFC V2 0/8] virtio: migrate new properties Alexander Graf
2014-05-19 12:45 ` Greg Kurz
2014-05-19 13:07 ` Alexander Graf
2014-05-19 15:10 ` Michael S. Tsirkin
2014-05-19 15:36 ` Alexander Graf
2014-05-19 15:50 ` Michael S. Tsirkin
2014-05-19 15:40 ` Andreas Färber
2014-05-19 15:53 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2014-05-14 15:41 [Qemu-devel] [PATCH RFC " Greg Kurz
2014-05-14 15:42 ` [Qemu-devel] [PATCH RFC 8/8] virtio: add endian-ambivalent support to VirtIODevice Greg Kurz
[not found] ` <5384A8D2.8050104@redhat.com>
[not found] ` <20140529111253.4ff55199@bahia.local>
[not found] ` <538708FA.4070309@redhat.com>
2014-06-12 7:43 ` Greg Kurz
2014-06-12 7:54 ` Michael S. Tsirkin
2014-06-12 8:47 ` Greg Kurz
2014-06-12 9:05 ` Michael S. Tsirkin
2014-06-12 9:06 ` Alexander Graf
2014-06-12 8:55 ` Alexander Graf
2014-06-12 9:07 ` Michael S. Tsirkin
2014-06-12 9:08 ` Alexander Graf
2014-06-12 8:55 ` Paolo Bonzini
2014-06-12 8:57 ` Alexander Graf
2014-06-12 9:06 ` Greg Kurz
2014-06-12 9:19 ` Paolo Bonzini
2014-06-12 9:37 ` Michael S. Tsirkin
2014-06-12 9:39 ` Paolo Bonzini
2014-06-12 9:43 ` Alexander Graf
2014-06-12 10:14 ` Greg Kurz
2014-06-12 10:39 ` Alexander Graf
2014-06-12 10:50 ` Greg Kurz
2014-06-12 10:58 ` Alexander Graf
2014-06-12 10:59 ` Michael S. Tsirkin
2014-06-12 11:10 ` Greg Kurz
2014-06-12 10:57 ` Michael S. Tsirkin
2014-06-12 10:56 ` Michael S. Tsirkin
2014-06-12 10:55 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537A3A1F.8010303@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=amit.shah@redhat.com \
--cc=famz@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).