[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH REPOST v3 78/80] hostmem: fix strict bind policy
From: |
Halil Pasic |
Subject: |
Re: [PATCH REPOST v3 78/80] hostmem: fix strict bind policy |
Date: |
Fri, 24 Jan 2020 20:17:48 +0100 |
On Thu, 23 Jan 2020 12:38:43 +0100
Igor Mammedov <address@hidden> wrote:
> With main RAM now converted to hostmem backends, there is no
> point in keeping global mem_prealloc around, so alias
> -mem-prealloc to "memory-backend.prealloc=on"
> machine compat[*] property and make mem_prealloc a local
> variable to only stir registration of compat property.
>
> *) currently user accessible -global works only with DEVICE
> based objects and extra work is needed to make it work
> with hostmem backends. But that is convenience option
> and out of scope of this already huge refactoring.
> Hence machine compat properties were used.
AFAIU because of this something like
-global memory-backend-file.share=on
(as proposed by
https://lists.nongnu.org/archive/html/qemu-devel/2019-12/msg00531.html)
can not be used to make the main RAM shared (e.g. for vhost on s390x).
Or am I wrong? If not, is -global still the way we want to make this work
for non-numa machines, or did I miss updates?
Regards,
Halil
- Re: [PATCH REPOST v3 74/80] exec: cleanup qemu_minrampagesize()/qemu_maxrampagesize(), (continued)
[PATCH REPOST v3 73/80] remove no longer used memory_region_allocate_system_memory(), Igor Mammedov, 2020/01/23
[PATCH REPOST v3 79/80] tests:numa-test: make top level args dynamic and g_autofree(cli) cleanups, Igor Mammedov, 2020/01/23
[PATCH REPOST v3 80/80] tests:numa-test: use explicit memdev to specify node RAM, Igor Mammedov, 2020/01/23