[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu
From: |
Peter Xu |
Subject: |
Re: [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu |
Date: |
Thu, 23 Feb 2023 10:47:05 -0500 |
On Thu, Feb 23, 2023 at 02:59:19PM +0800, Jason Wang wrote:
> Hi All:
>
> According to ATS, device should work if ATS is disabled. This is not
> correctly implemented in the current intel-iommu since it doesn't
> handle the UNMAP notifier correctly. This breaks the vhost-net +
> vIOMMU without dt.
>
> The root casue is that the when there's a device IOTLB miss (note that
> it's not specific to PCI so it can work without ATS), Qemu doesn't
> build the IOVA tree, so when guest start an IOTLB invalidation, Qemu
> won't trigger the UNMAP notifier.
>
> Fixing this by triggering UNMAP notifier in those cases.
Maybe someday we should start merging different places where we used the
same IOMMU_NOTIFIER_UNMAP event and also taking care of truncation of
notifier ranges within memory.c, but that can definitely be done later.
Reviewed-by: Peter Xu <peterx@redhat.com>
Thanks, Jason!
--
Peter Xu
- [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu, Jason Wang, 2023/02/23
- [PATCH V2 1/5] intel-iommu: fail MAP notifier without caching mode, Jason Wang, 2023/02/23
- [PATCH V2 2/5] intel-iommu: fail DEVIOTLB_UNMAP without dt mode, Jason Wang, 2023/02/23
- [PATCH V2 3/5] memory: introduce memory_region_unmap_iommu_notifier_range(), Jason Wang, 2023/02/23
- [PATCH V2 4/5] smmu: switch to use memory_region_unmap_iommu_notifier_range(), Jason Wang, 2023/02/23
- [PATCH V2 5/5] intel-iommu: send UNMAP notifications for domain or global inv desc, Jason Wang, 2023/02/23
- Re: [PATCH V2 0/5] Fix UNMAP notifier for intel-iommu,
Peter Xu <=