diff options
| author | Igor Mammedov <imammedo@redhat.com> | 2020-04-30 11:46:06 -0400 |
|---|---|---|
| committer | Eduardo Habkost <ehabkost@redhat.com> | 2020-05-12 12:48:57 -0400 |
| commit | 70b6d525dfb51d5e523d568d1139fc051bc223c5 (patch) | |
| tree | d074d23bb88164f58180f4c5db6a09c78e2dea4a /hw/adc/stm32f2xx_adc.c | |
| parent | de2f658b6bb422ec0e0fa94a49e476018602eeea (diff) | |
| download | focaccia-qemu-70b6d525dfb51d5e523d568d1139fc051bc223c5.tar.gz focaccia-qemu-70b6d525dfb51d5e523d568d1139fc051bc223c5.zip | |
hostmem: don't use mbind() if host-nodes is empty
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM. The backend however calls mbind() which is typically NOP in case of default policy/absent host-nodes bitmap. However when runing in container with black-listed mbind() syscall, QEMU fails to start with error "cannot bind memory to host NUMA nodes: Operation not permitted" even when user hasn't provided host-nodes to pin to explictly (which is the case with -m option) To fix issue, call mbind() only in case when user has provided host-nodes explicitly (i.e. host_nodes bitmap is not empty). That should allow to run QEMU in containers with black-listed mbind() without memory pinning. If QEMU provided memory-pinning is required user still has to white-list mbind() in container configuration. Reported-by: Manuel Hohmann <mhohmann@physnet.uni-hamburg.de> Signed-off-by: Igor Mammedov <imammedo@redhat.com> Message-Id: <20200430154606.6421-1-imammedo@redhat.com> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com> Cc: qemu-stable@nongnu.org Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'hw/adc/stm32f2xx_adc.c')
0 files changed, 0 insertions, 0 deletions