-
- Downloads
virtio: replace restricted mem access flag with callback
Instead of having a global flag to require restricted memory access for all virtio devices, introduce a callback which can select that requirement on a per-device basis. For convenience add a common function returning always true, which can be used for use cases like SEV. Per default use a callback always returning false. As the callback needs to be set in early init code already, add a virtio anchor which is builtin in case virtio is enabled. Signed-off-by:Juergen Gross <jgross@suse.com> Tested-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> # Arm64 guest using Xen Reviewed-by:
Stefano Stabellini <sstabellini@kernel.org> Link: https://lore.kernel.org/r/20220622063838.8854-2-jgross@suse.com Signed-off-by:
Juergen Gross <jgross@suse.com>
Showing
- arch/s390/mm/init.c 2 additions, 2 deletionsarch/s390/mm/init.c
- arch/x86/mm/mem_encrypt_amd.c 2 additions, 2 deletionsarch/x86/mm/mem_encrypt_amd.c
- drivers/virtio/Kconfig 4 additions, 0 deletionsdrivers/virtio/Kconfig
- drivers/virtio/Makefile 1 addition, 0 deletionsdrivers/virtio/Makefile
- drivers/virtio/virtio.c 2 additions, 2 deletionsdrivers/virtio/virtio.c
- drivers/virtio/virtio_anchor.c 18 additions, 0 deletionsdrivers/virtio/virtio_anchor.c
- include/linux/platform-feature.h 1 addition, 5 deletionsinclude/linux/platform-feature.h
- include/linux/virtio_anchor.h 19 additions, 0 deletionsinclude/linux/virtio_anchor.h
- include/xen/xen.h 2 additions, 2 deletionsinclude/xen/xen.h
Loading
Please register or sign in to comment