Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread David Hildenbrand
On 27.11.24 11:50, David Hildenbrand wrote: RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever and map whatever you want in there. Likely you would need a distinct RAMBlock/RAM memory region per mmap(), and would end up mmaping implicitly via qemu_ram_mmap(). Then, your sh

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread Albert Esteve
On Wed, Nov 27, 2024 at 11:50 AM David Hildenbrand wrote: > > > >> RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever > >> and map whatever you want in there. > >> > >> Likely you would need a distinct RAMBlock/RAM memory region per mmap(), > >> and would end up mmaping implici

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread David Hildenbrand
On 27.11.24 13:31, Albert Esteve wrote: On Wed, Nov 27, 2024 at 1:18 PM David Hildenbrand wrote: On 27.11.24 13:10, David Hildenbrand wrote: On 27.11.24 11:50, David Hildenbrand wrote: RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever and map whatever you want in there

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread Albert Esteve
On Wed, Nov 27, 2024 at 1:18 PM David Hildenbrand wrote: > > On 27.11.24 13:10, David Hildenbrand wrote: > > On 27.11.24 11:50, David Hildenbrand wrote: > >> > RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever > and map whatever you want in there. > > Likel

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread David Hildenbrand
On 27.11.24 13:10, David Hildenbrand wrote: On 27.11.24 11:50, David Hildenbrand wrote: RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever and map whatever you want in there. Likely you would need a distinct RAMBlock/RAM memory region per mmap(), and would end up mmaping i

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-27 Thread David Hildenbrand
RAM memory region/ RAMBlock that has properly set flags/fd/whatssoever and map whatever you want in there. Likely you would need a distinct RAMBlock/RAM memory region per mmap(), and would end up mmaping implicitly via qemu_ram_mmap(). Then, your shared region would simply be an empty contain

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-25 Thread Albert Esteve
On Mon, Sep 16, 2024 at 7:21 PM Stefan Hajnoczi wrote: > > On Thu, Sep 12, 2024 at 04:53:31PM +0200, Albert Esteve wrote: > > Add SHMEM_MAP/UNMAP requests to vhost-user to > > handle VIRTIO Shared Memory mappings. > > > > This request allows backends to dynamically map > > fds into a VIRTIO Shared

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-11-25 Thread Albert Esteve
On Tue, Sep 17, 2024 at 12:08 PM David Hildenbrand wrote: > > On 12.09.24 16:53, Albert Esteve wrote: > > Add SHMEM_MAP/UNMAP requests to vhost-user to > > handle VIRTIO Shared Memory mappings. > > > > This request allows backends to dynamically map > > fds into a VIRTIO Shared Memory Region inden

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-09-17 Thread David Hildenbrand
On 12.09.24 16:53, Albert Esteve wrote: Add SHMEM_MAP/UNMAP requests to vhost-user to handle VIRTIO Shared Memory mappings. This request allows backends to dynamically map fds into a VIRTIO Shared Memory Region indentified by its `shmid`. Then, the fd memory is advertised to the driver as a base

Re: [PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-09-16 Thread Stefan Hajnoczi
On Thu, Sep 12, 2024 at 04:53:31PM +0200, Albert Esteve wrote: > Add SHMEM_MAP/UNMAP requests to vhost-user to > handle VIRTIO Shared Memory mappings. > > This request allows backends to dynamically map > fds into a VIRTIO Shared Memory Region indentified > by its `shmid`. Then, the fd memory is a

[PATCH v3 1/5] vhost-user: Add VIRTIO Shared Memory map request

2024-09-12 Thread Albert Esteve
Add SHMEM_MAP/UNMAP requests to vhost-user to handle VIRTIO Shared Memory mappings. This request allows backends to dynamically map fds into a VIRTIO Shared Memory Region indentified by its `shmid`. Then, the fd memory is advertised to the driver as a base addres + offset, so it can be read/writte