From: Rusty Russell <rusty@rustcorp.com.au>
To: quintela@redhat.com
Cc: QEMU-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] vmstate conversion for virtio?
Date: Wed, 05 Dec 2012 09:47:22 +1030 [thread overview]
Message-ID: <87r4n5h0fx.fsf@rustcorp.com.au> (raw)
In-Reply-To: <87zk1uca8z.fsf@elfo.mitica>
Juan Quintela <quintela@redhat.com> writes:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Hi all,
>>
>> I want to rework the qemu virtio subsystem, but various
>> structures are currently blatted to disk in save/load. So I looked at
>> altering that, only to discover that it needs conversion to vmstate, and
>> 2009 patches in patchwork which have never been applied.
>>
>> Has there been any progress on this? A git tree I should be using?
>
> My trees are more than 1 year old, and unfinished (basic trouble is how
> to express the lists of pending requests for block and now serial). I
> haven't yet looked at virtio-scsi.
That's the easy part though, and part of what I want to change.
All we need is the index of the request; the rest can be re-read from
the ring. So create the array in pre_save, and restore on post_load.
Is there something more recent than
http://repo.or.cz/w/qemu/quintela.git/shortlog/refs/heads/vmstate/virtio
or should I cherry-pick from there?
Thanks,
Rusty.
next prev parent reply other threads:[~2012-12-04 23:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 3:09 [Qemu-devel] vmstate conversion for virtio? Rusty Russell
2012-12-04 6:30 ` Michael S. Tsirkin
2012-12-04 11:44 ` Juan Quintela
2012-12-04 23:17 ` Rusty Russell [this message]
2012-12-05 11:08 ` [Qemu-devel] [PATCH] virtio: verify that all outstanding buffers are flushed (was Re: vmstate conversion for virtio?) Michael S. Tsirkin
2012-12-06 6:03 ` Rusty Russell
2012-12-06 8:02 ` Michael S. Tsirkin
2012-12-06 23:39 ` Rusty Russell
2012-12-10 14:16 ` Anthony Liguori
2012-12-10 23:54 ` Rusty Russell
2012-12-10 20:35 ` 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=87r4n5h0fx.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.