> hoping that RPMSG-over-VIRTIO would be easily adapted to what we need. > If we have to create a new virtio device (that is nearly identical to > rpmsg), that is going to push-out SR-IOV support a great deal, plus > requiring cloning of a lot of existing code for a new purpose. Duplication of code would not be a viable way forward. Reusing/enhancing/fixing what is currently available is definitely a better option. > > Our only other alternative is to do something to allow guest-host > communication to use the fabric loopback, which is not at all desirable > and has many issues of its own. > > > > >> Is this the correct way to use RPMSG-over-VIRTIO? If so, what actions > >> need to be taken to cause a "rpmsg_ctl" device to be created? What > >> method would be used (in a kernel driver) to get a pointer to the > >> "rpmsg_ctl" device, for use with rpmsg_create_channel()? > >> > >>> Thanks, > >>> Doug > >>> > >> External recipient > > > External recipient
