Re: [PATCH RFC 00/15] virtio-mem: Expose device memory via separate memslots

2021-10-14 Thread David Hildenbrand
On 13.10.21 21:03, Dr. David Alan Gilbert wrote: > * David Hildenbrand (da...@redhat.com) wrote: >> Based-on: 20211011175346.15499-1-da...@redhat.com >> >> A virtio-mem device is represented by a single large RAM memory region >> backed by a single large mmap. >> >> Right now, we map that complete

Re: [PATCH RFC 00/15] virtio-mem: Expose device memory via separate memslots

2021-10-13 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > Based-on: 20211011175346.15499-1-da...@redhat.com > > A virtio-mem device is represented by a single large RAM memory region > backed by a single large mmap. > > Right now, we map that complete memory region into guest physical addres > space, resul

[PATCH RFC 00/15] virtio-mem: Expose device memory via separate memslots

2021-10-13 Thread David Hildenbrand
Based-on: 20211011175346.15499-1-da...@redhat.com A virtio-mem device is represented by a single large RAM memory region backed by a single large mmap. Right now, we map that complete memory region into guest physical addres space, resulting in a very large memory mapping, KVM memory slot, ... al