Hello,
I was under the impression that the each virtio driver will have a frontend and
backend part. The frontend part would be loaded in the Guest OS and the backend
driver will be loaded in the Host OS. These two drivers will communicate with
each other. The backend driver will then
On Mon, Nov 22, 2010 at 2:05 PM, Prasad Joshi
p.g.jo...@student.reading.ac.uk wrote:
I was under the impression that the each virtio driver will have a frontend
and backend part. The frontend part would be loaded in the Guest OS and the
backend driver will be loaded in the Host OS. These two
Michael S. Tsirkin wrote:
Hi!
I see this in virtio_ring.c:
/* Put entry in available array (but don't update avail-idx *
until they do sync). */
Why is it done this way?
It seems that updating the index straight away would be simpler, while
this might allow the host to
Hi!
I see this in virtio_ring.c:
/* Put entry in available array (but don't update avail-idx *
until they do sync). */
Why is it done this way?
It seems that updating the index straight away would be simpler, while
this might allow the host to specilatively look up the buffer
On Wed, May 05, 2010 at 02:40:15PM -0500, Anthony Liguori wrote:
On 05/05/2010 06:09 AM, Michael S. Tsirkin wrote:
Hi!
I see this in virtio_ring.c:
/* Put entry in available array (but don't update avail-idx *
until they do sync). */
Why is it done this way?
It seems that
On Wed, 5 May 2010 08:39:47 pm Michael S. Tsirkin wrote:
Hi!
I see this in virtio_ring.c:
/* Put entry in available array (but don't update avail-idx *
until they do sync). */
Why is it done this way?
It seems that updating the index straight away would be simpler, while
