> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] > Sent: Friday, March 17, 2017 4:49 AM
<...> > I think there is one interesting technological point in this thread. > We are discussing about IVSHMEM but its support by Qemu is confused. > This feature is not in the MAINTAINERS file of Qemu. > Please Qemu maintainers, what is the future of IVSHMEM? I need to clarify a technical point. AVP is not ivshmem; at least not in the strict sense of the term. We initially started out using ivshmem as-is but then we needed to fork from that in order to add functionality that we needed to better integrate with our solution. AVP is now a separate Wind River specific extension completely independent of any past ivshmem implementation. I used the term ivshmem in the documentation to provide context to the reader to understand, by comparison, what type of shared memory model we are using. I can remove that reference if it leads to confusion or a desire to make direct comparisons with ivshmem.
