Displaying 4 results from an estimated 4 matches for "virtio_arch_finalize_featur".
Did you mean:
virtio_arch_finalize_features
2020 Jun 17
4
[PATCH v3 1/1] s390: virtio: let arch accept devices without IOMMU feature
...does
the job of preventing calamity, and the details can be changed any time,
thus:
Acked-by: Halil Pasic <pasic at linux.ibm.com>
Regarding the interaction of architecture specific code with virtio core,
I believe we could have made the interface more generic.
One option is to introduce virtio_arch_finalize_features(), a hook that
could reject any feature that is inappropriate.
Another option would be to find a common name for is_prot_virt_guest()
(arch/s390) sev_active() (arch/x86) and is_secure_guest() (arch/powerpc)
and use that instead of arch_needs_virtio_iommu_platform() and where-ever
appropriate. Cu...
2020 Jun 17
4
[PATCH v3 1/1] s390: virtio: let arch accept devices without IOMMU feature
...does
the job of preventing calamity, and the details can be changed any time,
thus:
Acked-by: Halil Pasic <pasic at linux.ibm.com>
Regarding the interaction of architecture specific code with virtio core,
I believe we could have made the interface more generic.
One option is to introduce virtio_arch_finalize_features(), a hook that
could reject any feature that is inappropriate.
Another option would be to find a common name for is_prot_virt_guest()
(arch/s390) sev_active() (arch/x86) and is_secure_guest() (arch/powerpc)
and use that instead of arch_needs_virtio_iommu_platform() and where-ever
appropriate. Cu...
2020 Jun 19
0
[PATCH v3 1/1] s390: virtio: let arch accept devices without IOMMU feature
...d the details can be changed any time,
> thus:
>
> Acked-by: Halil Pasic <pasic at linux.ibm.com>
>
> Regarding the interaction of architecture specific code with virtio core,
> I believe we could have made the interface more generic.
>
> One option is to introduce virtio_arch_finalize_features(), a hook that
> could reject any feature that is inappropriate.
s/any feature/any combination of features/
This sounds like a good idea (for a later update).
>
> Another option would be to find a common name for is_prot_virt_guest()
> (arch/s390) sev_active() (arch/x86) and is_se...
2020 Jun 17
6
[PATCH v3 0/1] s390: virtio: let arch choose to accept devices without IOMMU feature
An architecture protecting the guest memory against unauthorized host
access may want to enforce VIRTIO I/O device protection through the
use of VIRTIO_F_IOMMU_PLATFORM.
Let's give a chance to the architecture to accept or not devices
without VIRTIO_F_IOMMU_PLATFORM.
Pierre Morel (1):
s390: virtio: let arch accept devices without IOMMU feature
arch/s390/mm/init.c | 6 ++++++