On Thu, Dec 5, 2024 at 1:19 AM Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote: > > On Wed, 4 Dec 2024 at 10:38, <t.ampelikiotis@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > From: Timos Ampelikiotis <t.ampelikiotis@xxxxxxxxxxxxxxxxxxxxxx> > > > > We would like to share with you an RFC for the Virtio-loopback > > technology which we have been working on at Virtual Open Systems in > > the context of the Automotive Grade Linux community (Software defined > > Vehicles expert group) > > > > We previously presented this activity (see [1]) and now we come back > > to you with latest development and updates. > > > > We believe that the technology is more mature today and we would like > > to assess the community interest in the technology itself and in > > merging the code. > > > > Below we provide a brief description of the technology, recent > > updates and a short comparison with vDUSE that might be seen as a > > similar technology. > > > > 1. Overview: > > ------- > > > > Virtio-loopback is a hardware abstraction layer (HAL) designed for > > non-virtualized environments based on virtio. The main objective is > > to enable applications communication with vhost-user devices in a > > non-virtualized environment. > > I don't see anything related to vhost-user in the patch. It seems to > be a virtio-mmio interface between the kernel driver and userspace? Yes, it works like a kernel virtio transport. So it can only talk to kernel drivers. If this approach turns out to be useful, I would rather make it a new memory model for VDUSE. (VDUSE is flexible to support more than just the current iova domain). It would be a converged solution and the management plane would be reused. Thanks > > Stefan >
