Ian Jackson 0ef4d87da5 xen: restrict: use xentoolcore_restrict_all ... And insist that it works. Drop individual use of xendevicemodel_restrict and xenforeignmemory_restrict. These are not actually effective in this version of qemu, because qemu has a large number of fds open onto various Xen control devices. The restriction arrangements are still not right, because the restriction needs to be done very late - after qemu has opened all of its control fds. xentoolcore_restrict_all and xentoolcore.h are available in Xen 4.10 and later, only. Provide a compatibility stub. And drop the compatibility stubs for the old functions. Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com> Reviewed-by: Anthony PERARD <anthony.perard@citrix.com> Acked-by: Stefano Stabellini <sstabellini@kernel.org>		2018-04-26 16:29:51 +01:00
..
io	xen: import ring.h from xen	2017-04-21 12:41:29 -07:00
xen.h	xen: use libxendevice model to restrict operations	2017-04-21 12:40:14 -07:00
xen_backend.h	xen: add a global indicator for grant copy being available	2017-10-26 14:23:06 -07:00
xen_common.h	xen: restrict: use xentoolcore_restrict_all	2018-04-26 16:29:51 +01:00
xen_pvdev.h	xen: create qdev for each backend device	2016-11-22 10:29:39 -08:00