On May 4, 2022 3:57:03 PM UTC, Juergen Gross <jgross@xxxxxxxx> wrote: >Instead of using arch_has_restricted_virtio_memory_access() together >with CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, replace those >with platform_has() and a new platform feature >PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS. > >Signed-off-by: Juergen Gross <jgross@xxxxxxxx> >--- >V2: >- move setting of PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS in SEV case > to sev_setup_arch(). >V3: >- remove Hyper-V chunk (Michael Kelley) >- remove include virtio_config.h from mem_encrypt.c (Oleksandr Tyshchenko) >- add comment for PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS (Oleksandr Tyshchenko) >--- > arch/s390/Kconfig | 1 - > arch/s390/mm/init.c | 13 +++---------- > arch/x86/Kconfig | 1 - > arch/x86/mm/mem_encrypt.c | 7 ------- > arch/x86/mm/mem_encrypt_amd.c | 4 ++++ > drivers/virtio/Kconfig | 6 ------ > drivers/virtio/virtio.c | 5 ++--- > include/linux/platform-feature.h | 6 +++++- > include/linux/virtio_config.h | 9 --------- > 9 files changed, 14 insertions(+), 38 deletions(-) Acked-by: Borislav Petkov <bp@xxxxxxx> -- Sent from a device which is ok for reading mail but awful for writing. Please excuse any shortcomings. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
