Displaying 11 results from an estimated 11 matches for "5809e5f5b157".
2020 Aug 21
1
[PATCH v9 1/2] virtio: let arch advertise guest's memory access restrictions
...ibm.com>
> ---
> drivers/virtio/Kconfig | 6 ++++++
> drivers/virtio/virtio.c | 15 +++++++++++++++
> include/linux/virtio_config.h | 9 +++++++++
> 3 files changed, 30 insertions(+)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..509f3b4d8ba1 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
> + b...
2020 Aug 19
4
[PATCH v9 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.
in this respin:
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,
and the config
2020 Aug 18
4
[PATCH v8 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.
in this respin:
I use the original idea from Connie for an optional
arch_has_restricted_memory_access.
I renamed the callback accordingly, added the definition of
ARCH_HAS_RESTRICTED_MEMORY_ACCESS inside the VIRTIO Kconfig
and the selection in the PROTECTED_VIRTUALIZATION_GUEST
config
2020 Jun 19
0
[PATCH] virtio-mem: Fix build error due to improper use 'select'
...s://bugzilla.kernel.org/show_bug.cgi?id=208245
>
> Signed-off-by: Weilong Chen <chenweilong at huawei.com>
> ---
> drivers/virtio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..5c92e4a50882 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -85,7 +85,7 @@ config VIRTIO_MEM
> depends on VIRTIO
> depends on MEMORY_HOTPLUG_SPARSE
> depends on MEMORY_HOTREMOVE
> - select CONTIG_ALLOC
> + depends on CONTIG_ALLOC
>...
2020 Jun 19
0
[PATCH] virtio-mem: Fix build error due to improper use 'select'
...en <chenweilong at huawei.com>
Cc virtio mem maintainer:
M: David Hildenbrand <david at redhat.com>
> ---
> drivers/virtio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..5c92e4a50882 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -85,7 +85,7 @@ config VIRTIO_MEM
> depends on VIRTIO
> depends on MEMORY_HOTPLUG_SPARSE
> depends on MEMORY_HOTREMOVE
> - select CONTIG_ALLOC
> + depends on CONTIG_ALLOC
> help...
2020 Jun 19
0
[PATCH] virtio-mem: Fix build error due to improper use 'select'
...David Hildenbrand <david at redhat.com>
>
> Signed-off-by: Weilong Chen <chenweilong at huawei.com>
> ---
> drivers/virtio/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..5c92e4a50882 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -85,7 +85,7 @@ config VIRTIO_MEM
> depends on VIRTIO
> depends on MEMORY_HOTPLUG_SPARSE
> depends on MEMORY_HOTREMOVE
> - select CONTIG_ALLOC
> + depends on CONTIG_ALLOC
> help...
2020 Aug 18
0
[PATCH v8 1/2] virtio: let arch validate VIRTIO features
...res.
Signed-off-by: Pierre Morel <pmorel at linux.ibm.com>
---
drivers/virtio/Kconfig | 6 ++++++
drivers/virtio/virtio.c | 4 ++++
include/linux/virtio_config.h | 9 +++++++++
3 files changed, 19 insertions(+)
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 5809e5f5b157..eef09e3c92f9 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_MEMORY_ACCESS
+ bool
+ help
+ This option is selected by any a...
2020 Aug 19
0
[PATCH v9 1/2] virtio: let arch advertise guest's memory access restrictions
...ff-by: Pierre Morel <pmorel at linux.ibm.com>
---
drivers/virtio/Kconfig | 6 ++++++
drivers/virtio/virtio.c | 15 +++++++++++++++
include/linux/virtio_config.h | 9 +++++++++
3 files changed, 30 insertions(+)
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 5809e5f5b157..509f3b4d8ba1 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 b...
2020 Aug 18
2
[PATCH v8 1/2] virtio: let arch validate VIRTIO features
...orel at linux.ibm.com>
> ---
> drivers/virtio/Kconfig | 6 ++++++
> drivers/virtio/virtio.c | 4 ++++
> include/linux/virtio_config.h | 9 +++++++++
> 3 files changed, 19 insertions(+)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..eef09e3c92f9 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_MEMORY_ACCESS
> + bool
>...
2020 Aug 18
2
[PATCH v8 1/2] virtio: let arch validate VIRTIO features
...orel at linux.ibm.com>
> ---
> drivers/virtio/Kconfig | 6 ++++++
> drivers/virtio/virtio.c | 4 ++++
> include/linux/virtio_config.h | 9 +++++++++
> 3 files changed, 19 insertions(+)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..eef09e3c92f9 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_MEMORY_ACCESS
> + bool
>...
2020 Aug 31
3
[PATCH v10 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,
and the config option to