On Mon, Nov 18, 2013 at 08:18:47AM -0800, Anthony Liguori wrote:
On Nov 18, 2013 7:05 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Mon, Nov 18, 2013 at 02:52:53PM +1000, Dave Airlie wrote:
So after talking to a few people at kvm forum I think the GPU code
should probably use the
On Mon, Nov 18, 2013 at 05:37:20PM +0100, Paolo Bonzini wrote:
Il 18/11/2013 16:03, Stefan Hajnoczi ha scritto:
As of today, there are still two vring implementations in
hw/virtio/virtio.c and hw/virtio/dataplane/vring.c. This means it isn't
clean and easy to integrate into a new device
On Mon, Nov 18, 2013 at 02:52:53PM +1000, Dave Airlie wrote:
So after talking to a few people at kvm forum I think the GPU code
should probably use the dataplane stuff from the outset,
The main advantages I think this gives me is being able to dequeue
objects from the vq from a thread and
On Nov 18, 2013 7:05 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Mon, Nov 18, 2013 at 02:52:53PM +1000, Dave Airlie wrote:
So after talking to a few people at kvm forum I think the GPU code
should probably use the dataplane stuff from the outset,
The main advantages I think this
Il 18/11/2013 16:03, Stefan Hajnoczi ha scritto:
As of today, there are still two vring implementations in
hw/virtio/virtio.c and hw/virtio/dataplane/vring.c. This means it isn't
clean and easy to integrate into a new device yet. Existing dataplane
devices basically take advantage of the
Hi,
So after talking to a few people at kvm forum I think the GPU code
should probably use the dataplane stuff from the outset,
The main advantages I think this gives me is being able to dequeue
objects from the vq from a thread and send irq vectors from there as
well.
Though since it appears