From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: QEMU-devel <qemu-devel@nongnu.org>, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio: verify that all outstanding buffers are flushed (was Re: vmstate conversion for virtio?)
Date: Thu, 6 Dec 2012 10:02:21 +0200 [thread overview]
Message-ID: <20121206080221.GC10837@redhat.com> (raw)
In-Reply-To: <87obi7g1k5.fsf@rustcorp.com.au>
On Thu, Dec 06, 2012 at 04:33:06PM +1030, Rusty Russell wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> > Add sanity check to address the following concern:
> >
> > On Wed, Dec 05, 2012 at 09:47:22AM +1030, Rusty Russell wrote:
> >> All we need is the index of the request; the rest can be re-read from
> >> the ring.
>
> The terminology I used here was loose, indeed.
>
> We need the head of the chained descriptor, which we already read from
> the ring when we gathered the request.
So ack that patch?
> Currently we dump a massive structure; it's inelegant at the very least.
>
> Cheers,
> Rusty.
Hmm not sure what you refer to. I see this per ring:
qemu_put_be32(f, vdev->vq[i].vring.num);
qemu_put_be64(f, vdev->vq[i].pa);
qemu_put_be16s(f, &vdev->vq[i].last_avail_idx);
Looks like there's no way around savng these fields.
--
MST
next prev parent reply other threads:[~2012-12-06 7:59 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
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 [this message]
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=20121206080221.GC10837@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rusty@rustcorp.com.au \
/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).