[virtio-dev] Re: virtio-iommu hotplug issue

2023-04-13 Thread Eric Auger
Hi, On 4/13/23 13:01, Akihiko Odaki wrote: > On 2023/04/13 19:40, Jean-Philippe Brucker wrote: >> Hello, >> >> On Thu, Apr 13, 2023 at 01:49:43PM +0900, Akihiko Odaki wrote: >>> Hi, >>> >>> Recently I encountered a problem with the combination of Linux's >>> virtio-iommu driver and QEMU when a

[virtio-dev] Re: [PATCH v3] virtio-iommu: Rework the bypass feature

2021-10-31 Thread Eric Auger
ow reads to a > @@ -538,6 +602,8 @@ \subsubsection{UNMAP request}\label{sec:Device Types / > IOMMU Device / Device ope > or be outside any mapping. The last address of a range MUST either be the > last address of a mapping or be outside any mapping. > > +The driver SHOULD NOT

Re: [virtio-dev] [PATCH] virtio-iommu: Rework the bypass feature

2021-10-31 Thread Eric Auger
Hi Jean, On 10/7/21 7:46 PM, Jean-Philippe Brucker wrote: > Hi Eric, > > On Wed, Oct 06, 2021 at 02:53:50PM +0200, Eric Auger wrote: >>> * The hypervisor can start the VM with bypass enabled or, if it knows >>> that the software stack supports it, disabled. The '

Re: [virtio-dev] [PATCH] virtio-iommu: Rework the bypass feature

2021-10-06 Thread Eric Auger
Hi Jean, On 9/30/21 6:35 PM, Jean-Philippe Brucker wrote: > The VIRTIO_IOMMU_F_BYPASS feature is awkward to use and incomplete. > Although it is implemented by QEMU, it is not supported by any driver as > far as I know. Replace it with a new VIRTIO_IOMMU_F_BYPASS_CONFIG > feature. The old feature