qemu-e2k/backends
Ilya Maximets 4a66c7a999 hostmem-memfd: disable for systems without sealing support
If seals are not supported, memfd_create() will fail.
Furthermore, there is no way to disable it in this case because
'.seal' property is not registered.

This issue leads to vhost-user-test failures on RHEL 7.2:

  qemu-system-x86_64: -object memory-backend-memfd,id=mem,size=2M,: \
                      failed to create memfd: Invalid argument

and actually breaks the feature on such systems.

Let's restrict memfd backend to systems with sealing support.

Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
Message-Id: <20190311135850.6537-2-i.maximets@samsung.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2019-03-11 17:16:56 -03:00
..
cryptodev-builtin.c cryptodev: add vhost support 2018-03-01 18:26:17 +02:00
cryptodev-vhost-user.c backends/cryptodev: remove dead code 2018-07-30 14:00:11 +02:00
cryptodev-vhost.c cryptodev: add vhost support 2018-03-01 18:26:17 +02:00
cryptodev.c Include less of the generated modular QAPI headers 2018-03-02 13:45:50 -06:00
hostmem-file.c hostmem-file: reject invalid pmem file sizes 2019-03-11 10:44:19 -03:00
hostmem-memfd.c hostmem-memfd: disable for systems without sealing support 2019-03-11 17:16:56 -03:00
hostmem-ram.c hostmem: use object id for memory region name with >= 4.0 2019-01-07 16:18:42 +04:00
hostmem.c hostmem: fix crash when querying empty host-nodes property via QMP 2019-03-06 11:51:08 -03:00
Makefile.objs vhost: restrict Linux dependency to kernel vhost 2019-02-21 12:28:01 -05:00
rng-egd.c
rng-random.c
rng.c
tpm.c