Displaying 3 results from an estimated 3 matches for "3999b411624c".
2020 Sep 07
0
[PATCH v11 1/2] virtio: let arch advertise guest's memory access restrictions
...ia Huck <cohuck at redhat.com>
---
drivers/virtio/Kconfig | 6 ++++++
drivers/virtio/virtio.c | 15 +++++++++++++++
include/linux/virtio_config.h | 10 ++++++++++
3 files changed, 31 insertions(+)
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 5c92e4a50882..3999b411624c 100644
--- a/drivers/virtio/Kconfig
+++ b/drivers/virtio/Kconfig
@@ -6,6 +6,12 @@ config VIRTIO
bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
or CONFIG_S390_GUEST.
+config ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS
+ bool
+ help
+ This option is selected if the architec...
2020 Sep 07
8
[PATCH v11 0/2] s390: virtio: let arch validate VIRTIO features
Hi all,
The goal of the series is to give a chance to the architecture
to validate VIRTIO device features.
The tests are back to virtio_finalize_features.
No more argument for the architecture callback which only reports
if the architecture needs guest memory access restrictions for
VIRTIO.
I renamed the callback to arch_has_restricted_virtio_memory_access,
the config option to
2020 Sep 07
8
[PATCH v11 0/2] s390: virtio: let arch validate VIRTIO features
Hi all,
The goal of the series is to give a chance to the architecture
to validate VIRTIO device features.
The tests are back to virtio_finalize_features.
No more argument for the architecture callback which only reports
if the architecture needs guest memory access restrictions for
VIRTIO.
I renamed the callback to arch_has_restricted_virtio_memory_access,
the config option to