search for: register_rpmsg_driv

On Thu, Jun 18, 2020 at 12:39:40PM +0200, Guennadi Liakhovetski wrote: > On Thu, Jun 18, 2020 at 11:33:24AM +0200, Vincent Whitchurch wrote: > > By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), > > etc. That API is not tied to virtio in any way and there are other > > non-virtio backends for this API in the tree. So it seems quite natural > > to implement a vhost backend for this API so that both sides of the link > > can use the same API but d...

On Thu, Jun 18, 2020 at 12:39:40PM +0200, Guennadi Liakhovetski wrote: > On Thu, Jun 18, 2020 at 11:33:24AM +0200, Vincent Whitchurch wrote: > > By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), > > etc. That API is not tied to virtio in any way and there are other > > non-virtio backends for this API in the tree. So it seems quite natural > > to implement a vhost backend for this API so that both sides of the link > > can use the same API but d...

...y of functions. Kernel vhost drivers simply > create a misc device and use the vhost functions for some common > functionality. This RPMsg vhost API stays in the same concept and provides > further functions for RPMsg specific vhost operation. By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), etc. That API is not tied to virtio in any way and there are other non-virtio backends for this API in the tree. So it seems quite natural to implement a vhost backend for this API so that both sides of the link can use the same API but different backends, instead of forcing th...

...y of functions. Kernel vhost drivers simply > create a misc device and use the vhost functions for some common > functionality. This RPMsg vhost API stays in the same concept and provides > further functions for RPMsg specific vhost operation. By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), etc. That API is not tied to virtio in any way and there are other non-virtio backends for this API in the tree. So it seems quite natural to implement a vhost backend for this API so that both sides of the link can use the same API but different backends, instead of forcing th...

On Thu, Jun 18, 2020 at 03:52:42PM +0200, Vincent Whitchurch wrote: > On Thu, Jun 18, 2020 at 12:39:40PM +0200, Guennadi Liakhovetski wrote: > > On Thu, Jun 18, 2020 at 11:33:24AM +0200, Vincent Whitchurch wrote: > > > By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), > > > etc. That API is not tied to virtio in any way and there are other > > > non-virtio backends for this API in the tree. So it seems quite natural > > > to implement a vhost backend for this API so that both sides of the link > > > can us...

...ost drivers simply > > create a misc device and use the vhost functions for some common > > functionality. This RPMsg vhost API stays in the same concept and provides > > further functions for RPMsg specific vhost operation. > > By the "normal rpmsg API" I mean register_rpmsg_driver(), rpmsg_send(), > etc. That API is not tied to virtio in any way and there are other > non-virtio backends for this API in the tree. So it seems quite natural > to implement a vhost backend for this API so that both sides of the link > can use the same API but different backends, i...

On Wed, May 27, 2020 at 08:05:41PM +0200, Guennadi Liakhovetski wrote: > Linux supports running the RPMsg protocol over the VirtIO transport > protocol, but currently there is only support for VirtIO clients and > no support for a VirtIO server. This patch adds a vhost-based RPMsg > server implementation. This looks really useful, but why is it implemented as an API and not as a real

On Wed, May 27, 2020 at 08:05:41PM +0200, Guennadi Liakhovetski wrote: > Linux supports running the RPMsg protocol over the VirtIO transport > protocol, but currently there is only support for VirtIO clients and > no support for a VirtIO server. This patch adds a vhost-based RPMsg > server implementation. This looks really useful, but why is it implemented as an API and not as a real