| commit | a3567ba1e6171ef7cfad55ae549c0cd8bffb1195 | |
| author | Pavel Fedin <p.fedin@samsung.com> | |
| Tue, 27 Oct 2015 12:51:31 +0000 (27 15:51 +0300) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Mon, 23 Nov 2015 12:43:38 +0000 (23 10:43 -0200) | ||
| tree | 832669b99e854d59e7189c9334a60d16508dc8f5 | treesnapshot (tar.gz zip) |
| parent | 541abd10a01da56c5f16582cd32d67114ec22a5c | commitdiff |
hostmem: Ignore ENOSYS while setting MPOL_DEFAULT
Currently hostmem backend fails if CONFIG_NUMA is enabled in QEMU
(the default) but NUMA is not supported by the kernel. This makes
it impossible to use ivshmem in such configurations.
This patch fixes the problem by ignoring ENOSYS error if policy is set to
MPOL_DEFAULT. This way the code behaves in the same way as if CONFIG_NUMA
was not defined. qemu will still fail if the user specifies some other
policy, so that the user knows it.
Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Currently hostmem backend fails if CONFIG_NUMA is enabled in QEMU
(the default) but NUMA is not supported by the kernel. This makes
it impossible to use ivshmem in such configurations.
This patch fixes the problem by ignoring ENOSYS error if policy is set to
MPOL_DEFAULT. This way the code behaves in the same way as if CONFIG_NUMA
was not defined. qemu will still fail if the user specifies some other
policy, so that the user knows it.
Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| backends/hostmem.c | diffblobblamehistory |