diff options
author | Ian Jackson <ian.jackson@eu.citrix.com> | 2017-09-15 16:03:14 +0100 |
---|---|---|
committer | Ian Jackson <Ian.Jackson@eu.citrix.com> | 2018-04-26 16:29:51 +0100 |
commit | 0ef4d87da58dfe0e0e466414701c103b7a44df65 (patch) | |
tree | a25a6bac8c41ca0b7328a7b217f92eb662225c6f /hw | |
parent | 58ea9a7a025243d3c34f869d4c5ea7c174235c4e (diff) | |
download | qemu-0ef4d87da58dfe0e0e466414701c103b7a44df65.zip |
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>
Diffstat (limited to 'hw')
0 files changed, 0 insertions, 0 deletions