Re: [PATCH v4 0/2] Allow memory_region_register_iommu_notifier() to fail

2019-09-27 Thread Paolo Bonzini
On 24/09/19 23:31, Alex Williamson wrote: > On Tue, 24 Sep 2019 10:25:15 +0200 > Eric Auger wrote: > >> This series allows the memory_region_register_iommu_notifier() >> to fail. As of now, when a MAP notifier is attempted to be >> registered along with SMMUv3 or AMD IOMMU, we exit in the IOMMU >

Re: [PATCH v4 0/2] Allow memory_region_register_iommu_notifier() to fail

2019-09-24 Thread Alex Williamson
On Tue, 24 Sep 2019 10:25:15 +0200 Eric Auger wrote: > This series allows the memory_region_register_iommu_notifier() > to fail. As of now, when a MAP notifier is attempted to be > registered along with SMMUv3 or AMD IOMMU, we exit in the IOMMU > MR notify_flag_changed() callback. > > In case of

Re: [PATCH v4 0/2] Allow memory_region_register_iommu_notifier() to fail

2019-09-24 Thread David Gibson
On Tue, Sep 24, 2019 at 10:25:15AM +0200, Eric Auger wrote: > This series allows the memory_region_register_iommu_notifier() > to fail. As of now, when a MAP notifier is attempted to be > registered along with SMMUv3 or AMD IOMMU, we exit in the IOMMU > MR notify_flag_changed() callback. > > In ca

[PATCH v4 0/2] Allow memory_region_register_iommu_notifier() to fail

2019-09-24 Thread Eric Auger
This series allows the memory_region_register_iommu_notifier() to fail. As of now, when a MAP notifier is attempted to be registered along with SMMUv3 or AMD IOMMU, we exit in the IOMMU MR notify_flag_changed() callback. In case of VFIO assigned device hotplug, this could be handled more nicely di