[PATCH 3/6] rpmsg: move common structures and defines to headers

virtio_rpmsg_bus.c keeps RPMsg protocol structure declarations and common defines like the ones, needed for name-space announcements, internal. Move them to common headers instead. Signed-off-by: Guennadi Liakhovetski --- drivers/rpmsg/virtio_rpmsg_bus.c | 78

[Q] vhost: returning misconfigured buffers

Hi, Many vhost drivers follow a common process to obtain and verify received buffers: head = vhost_get_vq_desc(vq, vq->iov, ARRAY_SIZE(vq->iov), , ,...); if (head < 0) { return ret; } if (head == vq->num) { /* no buffer */ return 0; /* or -EAGAIN or whatever */ } if (out

[Q] guest identification and host runtime PM

Hi, I'm working on a VirtIO / vhost audio virtualisation solution [1,2] and although it's already working rather well, some points still need clarification. 1. Guest identification. Is there a standard way to identify guests in a vhost driver? We need to send different audio topology to

0-copy (was Re: question: asynchronous notification from vhost)

On Tue, Oct 15, 2019 at 11:23:13AM +0200, Guennadi Liakhovetski wrote: > Hi, > > I'm developing a virtualised audio / DSP virtio and vhost driver pair > and I'm currently somewhat stuck trying to figure out how to > asynchronously notify the guest from the vhost dr

question: asynchronous notification from vhost

Hi, I'm developing a virtualised audio / DSP virtio and vhost driver pair and I'm currently somewhat stuck trying to figure out how to asynchronously notify the guest from the vhost driver. I'm using the vhost_add_used_and_signal() function to return data back to the guest in the guest

<    1   2