On Fri May 20, 2011 at 15:32:34 +0100, Stefan Hajnoczi wrote:
> > virtio_blk_alloc_request 0.000 req=0x91e08f0 -> Allocation 1
> > virtio_blk_alloc_request 77.659 req=0x9215650 -> Allocation 2
>
> Are you sure this isn't the temporary one that is allocated but freed
> immediately once the virtqueue is empty:
Good catch. Adding traces above both the qemu_free() calls I can
see that the allocation & freeing of VirtIOBlockReq structures
is paired.
Looks like I'm going to have to bite the bullet and do real allocation
tracking.
Steve Kemp
--
Bytemark Hosting
http://www.bytemark.co.uk/
phone UK: 0845 004 3 004
Dedicated Linux hosts from 15ukp ($30) per month
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
