Hi Sjur, On Tue, Feb 12, 2013 at 1:49 PM, <sjur.brandeland@xxxxxxxxxxxxxx> wrote: > From: Sjur Brændeland <sjur.brandeland@xxxxxxxxxxxxxx> > > Add functions for creating, deleting and kicking host-side virtio rings. > > The host ring is not integrated with virtiqueues and cannot be managed > through virtio-config. Is that an inherent design/issue of vringh or just a description of the current vringh code ? > Remoteproc must export functions for handling the host-side virtio rings. Have you considered exporting this via virtio instead ? > The functions rproc_virtio_get_vringh(), rproc_virtio_del_vringh(), > rproc_virtio_kick_vringh() are added to remoteproc_virtio.c. I wonder if this is the way we want things to work. Following this design, virtio drivers that use these rproc_* functions will be coupled with the remoteproc framework. One issue with this is what happens if, e.g., a VIRTIO_ID_CAIF vdev is added by other than remoteproc (e.g. by virtio_pci or virtio_mmio). Not sure how probable this really is, and whether there's anything that prevents this, but things will go awry if this happens. But maybe the important aspect to consider is whether we really want to couple virtio drivers (such as the upcoming caif one) with the remoteproc framework. If you'll take a look at the rpmsg virtio driver, there's nothing there which couples it with remoteproc. It's just a standard virtio driver, that can be easily used with traditional virtio hosts as well. This is possible of course thanks to the abstraction provided by virtio: remoteproc only implements a set of callbacks which virtio invokes when needed. Do we not want to follow a similar design scheme with vringh ? I have some other questions as well but maybe it's better to discuss first the bigger picture. Thanks! Ohad. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
