On (Tue) 20 Nov 2012 [19:44:55], Anthony Liguori wrote:
> Amit Shah writes:
>
> > Popping an elem from the vq just to find out its length causes problems
> > with save/load later on. Use the new virtqueue_get_avail_bytes()
> > function instead, saves us the complexity in the migration code, as w
Amit Shah writes:
> Popping an elem from the vq just to find out its length causes problems
> with save/load later on. Use the new virtqueue_get_avail_bytes()
> function instead, saves us the complexity in the migration code, as well
> as makes the migration endian-safe.
>
> Signed-off-by: Amit
Popping an elem from the vq just to find out its length causes problems
with save/load later on. Use the new virtqueue_get_avail_bytes()
function instead, saves us the complexity in the migration code, as well
as makes the migration endian-safe.
Signed-off-by: Amit Shah
---
hw/virtio-rng.c | 76
