Re: [Qemu-devel] [PATCH v2 33/42] ivshmem: Implement shm=... with a memory backend

Marc-André Lureau writes: > Hi > > On Wed, Mar 9, 2016 at 9:59 PM, Markus Armbruster wrote: >> The integrated memory backend has to go. >> >> Yes, my desugaring to memory-backend-file assumes Linux and the >> conventional mount point /dev/shm. >>

Re: [Qemu-devel] [PATCH v2 33/42] ivshmem: Implement shm=... with a memory backend

Hi On Wed, Mar 9, 2016 at 9:59 PM, Markus Armbruster wrote: > I didn't do this now, because one, I'm not aware of a system that needs > it, and two, ivshmem is Linux-specific anyway. ivshmem-plain could be > made more portable, and once that's done, memory-backend-shm might >

Re: [Qemu-devel] [PATCH v2 33/42] ivshmem: Implement shm=... with a memory backend

Marc-André Lureau writes: > Hi > > On Mon, Mar 7, 2016 at 8:25 PM, Markus Armbruster wrote: >> ivshmem has its very own code to create and map shared memory. >> Replace that with an implicitly created memory backend. Reduces the >> number of ways

Re: [Qemu-devel] [PATCH v2 33/42] ivshmem: Implement shm=... with a memory backend

Hi On Mon, Mar 7, 2016 at 8:25 PM, Markus Armbruster wrote: > ivshmem has its very own code to create and map shared memory. > Replace that with an implicitly created memory backend. Reduces the > number of ways we create BAR 2 from three to two. > > Signed-off-by: Markus

[Qemu-devel] [PATCH v2 33/42] ivshmem: Implement shm=... with a memory backend

ivshmem has its very own code to create and map shared memory. Replace that with an implicitly created memory backend. Reduces the number of ways we create BAR 2 from three to two. Signed-off-by: Markus Armbruster --- hw/misc/ivshmem.c | 79