Re: [PATCH] util/mmap: optimize qemu_ram_mmap() alignment

2023-04-11 Thread David Hildenbrand
On 11.04.23 16:39, Steven Sistare wrote: On 4/11/2023 3:57 AM, David Hildenbrand wrote: On 10.04.23 17:46, Steve Sistare wrote: Guest RAM created with memory-backend-memfd is aligned to a QEMU_VMALLOC_ALIGN=2M boundary, and memory-backend-memfd does not support the "align" parameter to change t

Re: [PATCH] util/mmap: optimize qemu_ram_mmap() alignment

2023-04-11 Thread Steven Sistare
On 4/11/2023 3:57 AM, David Hildenbrand wrote: > On 10.04.23 17:46, Steve Sistare wrote: >> Guest RAM created with memory-backend-memfd is aligned to a >> QEMU_VMALLOC_ALIGN=2M boundary, and memory-backend-memfd does not support >> the "align" parameter to change the default.  This is sub-optimal o

Re: [PATCH] util/mmap: optimize qemu_ram_mmap() alignment

2023-04-11 Thread David Hildenbrand
On 10.04.23 17:46, Steve Sistare wrote: Guest RAM created with memory-backend-memfd is aligned to a QEMU_VMALLOC_ALIGN=2M boundary, and memory-backend-memfd does not support the "align" parameter to change the default. This is sub-optimal on aarch64 kernels with a 64 KB page size and 512 MB huge

[PATCH] util/mmap: optimize qemu_ram_mmap() alignment

2023-04-10 Thread Steve Sistare
Guest RAM created with memory-backend-memfd is aligned to a QEMU_VMALLOC_ALIGN=2M boundary, and memory-backend-memfd does not support the "align" parameter to change the default. This is sub-optimal on aarch64 kernels with a 64 KB page size and 512 MB huge page size, as the range will not be backe