On Wed, Dec 12, 2012 at 04:55:47PM +0100, Stefan Hajnoczi wrote:
> On Tue, Dec 11, 2012 at 04:18:20PM +0200, Michael S. Tsirkin wrote:
> > On Mon, Dec 10, 2012 at 02:09:37PM +0100, Stefan Hajnoczi wrote:
> > > +iov->iov_base = hostmem_lookup(&vring->hostmem, desc.addr,
> > > desc.len,
> >
On Tue, Dec 11, 2012 at 04:18:20PM +0200, Michael S. Tsirkin wrote:
> On Mon, Dec 10, 2012 at 02:09:37PM +0100, Stefan Hajnoczi wrote:
> > +iov->iov_base = hostmem_lookup(&vring->hostmem, desc.addr,
> > desc.len,
> > + desc.flags & VRING_DESC_F_WRITE);
On Mon, Dec 10, 2012 at 02:09:37PM +0100, Stefan Hajnoczi wrote:
> +iov->iov_base = hostmem_lookup(&vring->hostmem, desc.addr, desc.len,
> + desc.flags & VRING_DESC_F_WRITE);
> +if (!iov->iov_base) {
> +error_report("Failed to map in
The virtio-blk-data-plane cannot access memory using the usual QEMU
functions since it executes outside the global mutex and the memory APIs
are this time are not thread-safe.
This patch introduces a virtqueue module based on the kernel's vhost
vring code. The trick is that we map guest memory ah
