iommu/s390: Further improvements
Niklas Schnelle
maintainercover iommu/s390: Further improvements
Hi All,
This series of patches improves the s390 IOMMU driver. These improvements help existing IOMMU users, mainly vfio-pci, but at the same time are also in preparation of converting s390 to use the common DMA API implementation in drivers/iommu/dma-iommu.c instead of its platform specific DMA API in arch/s390/pci/pci_dma.c that sidesteps the IOMMU driver to control the same hardware interface directly.
Among the included changes patch 1 improves the robustness of switching IOMMU domains and patch 2 adds the I/O TLB operations necessary for the DMA API conversion. Patches 3, 4, and 5 aim to improve performance with patch 5 being the most intrusive by removing the I/O translation table lock and using atomic updates instead.
This series goes on top of v7 of my previous series of IOMMU fixes[0] and similarly is available for easy testing in the iommu_improve_v1 branch with signed tag s390_iommu_improve_v1 of my git.kernel.org tree[1].
Best regards,
Niklas Schnelle
[0] https://lore.kernel.org/linux-iommu/[email protected]/
[1] https://git.kernel.org/pub/scm/linux/kernel/git/niks/linux.git/
Niklas Schnelle (5):
iommu/s390: Make attach succeed even if the device is in error state iommu/s390: Add I/O TLB ops
iommu/s390: Use RCU to allow concurrent domain_list iteration iommu/s390: Optimize IOMMU table walking
s390/pci: use lock-free I/O translation updates
arch/s390/include/asm/pci.h | 4 +- arch/s390/kvm/pci.c | 6 +- arch/s390/pci/pci.c | 13 +-- arch/s390/pci/pci_dma.c | 77 +++++++++------ drivers/iommu/s390-iommu.c | 180 ++++++++++++++++++++++++------------ 5 files changed, 183 insertions(+), 97 deletions(-)
Signature · 1 line
2.34.1
Niklas Schnelle
maintainerPATCH 1/5 iommu/s390: Make attach succeed even if the device is in error state
If a zPCI device is in the error state while switching IOMMU domains zpci_register_ioat() will fail and we would end up with the device not attached to any domain. In this state since zdev->dma_table == NULL a reset via zpci_hot_reset_device() would wrongfully re-initialize the device for DMA API usage using zpci_dma_init_device(). As automatic recovery is currently disabled while attached to an IOMMU domain this only affects slot resets triggered through other means but will affect automatic recovery once we switch to using dma-iommu.
Additionally with that switch common code expects attaching to the default domain to always work so zpci_register_ioat() should only fail if there is no chance to recover anyway, e.g. if the device has been unplugged.
Improve the robustness of attach by specifically looking at the status returned by zpci_mod_fc() to determine if the device is unavailable and in this case simply ignore the error. Once the device is reset zpci_hot_reset_device() will then correctly set the domain's DMA translation tables.
--- arch/s390/include/asm/pci.h | 2 +- arch/s390/kvm/pci.c | 6 ++++-- arch/s390/pci/pci.c | 11 ++++++----- arch/s390/pci/pci_dma.c | 3 ++- drivers/iommu/s390-iommu.c | 9 +++++++-- 5 files changed, 20 insertions(+), 11 deletions(-)
arch/s390/include/asm/pci.h +1 -1
@@ -221,7 +221,7 @@ void zpci_device_reserved(struct zpci_dev *zdev);bool zpci_is_device_configured (struct zpci_dev *zdev);int zpci_hot_reset_device (struct zpci_dev *zdev); -int zpci_register_ioat (struct zpci_dev *,u8 ,u64 ,u64 ,u64 ); +int zpci_register_ioat (struct zpci_dev *,u8 ,u64 ,u64 ,u64 ,u8 *);int zpci_unregister_ioat (struct zpci_dev *,u8 );void zpci_remove_reserved_devices (void );void zpci_update_fh (struct zpci_dev *zdev,u32 fh);
arch/s390/kvm/pci.c +4 -2
@@ -434,6 +434,7 @@ static void kvm_s390_pci_dev_release(struct zpci_dev *zdev)static int kvm_s390_pci_register_kvm (void *opaque,struct kvm *kvm) {struct zpci_dev *zdev = opaque; +u8 status;int rc;if (!zdev)
@@ -486,7 +487,7 @@ static int kvm_s390_pci_register_kvm(void *opaque, struct kvm *kvm)/* Re-register the IOMMU that was already created */ rc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status);if (rc) goto clear_gisa;
@@ -516,6 +517,7 @@ static void kvm_s390_pci_unregister_kvm(void *opaque) {struct zpci_dev *zdev = opaque;struct kvm *kvm; +u8 status;if (!zdev)return ;
@@ -554,7 +556,7 @@ static void kvm_s390_pci_unregister_kvm(void *opaque)/* Re-register the IOMMU that was already created */ zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status); out:spin_lock (&kvm->arch.kzdev_list_lock);
arch/s390/pci/pci.c +6 -5
@@ -116,20 +116,20 @@ EXPORT_SYMBOL_GPL(pci_proc_domain);/* Modify PCI: Register I/O address translation parameters */ int zpci_register_ioat (struct zpci_dev *zdev,u8 dmaas, -u64 base,u64 limit,u64 iota) +u64 base,u64 limit,u64 iota,u8 *status) {u64 req =ZPCI_CREATE_REQ (zdev->fh, dmaas,ZPCI_MOD_FC_REG_IOAT );struct zpci_fib fib = {0 }; -u8 cc, status; +u8 cc;WARN_ON_ONCE (iota &0x3fff ); fib.pba = base; fib.pal = limit; fib.iota = iota |ZPCI_IOTA_RTTO_FLAG ; fib.gd = zdev->gisa; - cc =zpci_mod_fc (req, &fib, &status); + cc =zpci_mod_fc (req, &fib, status);if (cc) -zpci_dbg (3 ,"reg ioat fid:%x, cc:%d, status:%d\n" , zdev->fid, cc, status); +zpci_dbg (3 ,"reg ioat fid:%x, cc:%d, status:%d\n" , zdev->fid, cc, *status);return cc; }EXPORT_SYMBOL_GPL (zpci_register_ioat);
@@ -764,6 +764,7 @@ EXPORT_SYMBOL_GPL(zpci_disable_device);*/ int zpci_hot_reset_device (struct zpci_dev *zdev) { +u8 status;int rc;zpci_dbg (3 ,"rst fid:%x, fh:%x\n" , zdev->fid, zdev->fh);
@@ -787,7 +788,7 @@ int zpci_hot_reset_device(struct zpci_dev *zdev)if (zdev->dma_table) rc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status);else rc =zpci_dma_init_device (zdev);if (rc) {
arch/s390/pci/pci_dma.c +2 -1
@@ -547,6 +547,7 @@ static void s390_dma_unmap_sg(struct device *dev, struct scatterlist *sg,int zpci_dma_init_device (struct zpci_dev *zdev) { +u8 status;int rc;/*
@@ -598,7 +599,7 @@ int zpci_dma_init_device(struct zpci_dev *zdev) }if (zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table))) { +virt_to_phys (zdev->dma_table), &status)) { rc = -EIO ; goto free_bitmap; }
drivers/iommu/s390-iommu.c +7 -2
@@ -98,6 +98,7 @@ static int s390_iommu_attach_device(struct iommu_domain *domain,struct s390_domain *s390_domain =to_s390_domain (domain);struct zpci_dev *zdev =to_zpci_dev (dev);unsigned long flags; +u8 status;int cc;if (!zdev)
@@ -113,8 +114,12 @@ static int s390_iommu_attach_device(struct iommu_domain *domain,zpci_dma_exit_device (zdev); cc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (s390_domain->dma_table)); -if (cc) +virt_to_phys (s390_domain->dma_table), &status); +/* +* If the device is undergoing error recovery the reset code +* will re-establish the new domain. +*/ +if (cc && status !=ZPCI_PCI_ST_FUNC_NOT_AVAIL )return -EIO ; zdev->dma_table = s390_domain->dma_table;
Signature · 1 line
2.34.1
Re: [PATCH 1/5] iommu/s390: Make attach succeed even if the device is in error state
Quoted 14 lines · Niklas Schnelle
If a zPCI device is in the error state while switching IOMMU domains
zpci_register_ioat()will fail and we would end up with the device not attached to any domain. In this state sincezdev->dma_table== NULL a reset viazpci_hot_reset_device()would wrongfully re-initialize the device for DMA API usage usingzpci_dma_init_device(). As automatic recovery is currently disabled while attached to an IOMMU domain this only affects slot resets triggered through other means but will affect automatic recovery once we switch to using dma-iommu.Additionally with that switch common code expects attaching to the default domain to always work so
zpci_register_ioat()should only fail if there is no chance to recover anyway, e.g. if the device has been unplugged.
Quoted 7 lines
Improve the robustness of attach by specifically looking at the status returned by
zpci_mod_fc()to determine if the device is unavailable and in this case simply ignore the error. Once the device is resetzpci_hot_reset_device()will then correctly set the domain's DMA translation tables.Signed-off-by Niklas Schnelle <[email protected]>
Seems reasonable to me.
Quoted 153 lines
--- arch/s390/include/asm/pci.h | 2 +- arch/s390/kvm/pci.c | 6 ++++-- arch/s390/pci/pci.c | 11 ++++++----- arch/s390/pci/pci_dma.c | 3 ++- drivers/iommu/s390-iommu.c | 9 +++++++-- 5 files changed, 20 insertions(+), 11 deletions(-)arch/s390/include/asm/pci.h +1
-1@@ -221,7 +221,7 @@ void zpci_device_reserved(struct zpci_dev *zdev);bool zpci_is_device_configured (struct zpci_dev *zdev);int zpci_hot_reset_device (struct zpci_dev *zdev); -int zpci_register_ioat (struct zpci_dev *,u8 ,u64 ,u64 ,u64 ); +int zpci_register_ioat (struct zpci_dev *,u8 ,u64 ,u64 ,u64 ,u8 *);int zpci_unregister_ioat (struct zpci_dev *,u8 );void zpci_remove_reserved_devices (void );void zpci_update_fh (struct zpci_dev *zdev,u32 fh);arch/s390/kvm/pci.c +4
-2@@ -434,6 +434,7 @@ static void kvm_s390_pci_dev_release(struct zpci_dev *zdev)static int kvm_s390_pci_register_kvm (void *opaque,struct kvm *kvm) {struct zpci_dev *zdev = opaque; +u8 status;int rc;if (!zdev)@@ -486,7 +487,7 @@ static int kvm_s390_pci_register_kvm(void *opaque, struct kvm *kvm)/* Re-register the IOMMU that was already created */ rc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status);if (rc) goto clear_gisa;@@ -516,6 +517,7 @@ static void kvm_s390_pci_unregister_kvm(void *opaque) {struct zpci_dev *zdev = opaque;struct kvm *kvm; +u8 status;if (!zdev)return ;@@ -554,7 +556,7 @@ static void kvm_s390_pci_unregister_kvm(void *opaque)/* Re-register the IOMMU that was already created */ zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status); out:spin_lock (&kvm->arch.kzdev_list_lock);arch/s390/pci/pci.c +6
-5@@ -116,20 +116,20 @@ EXPORT_SYMBOL_GPL(pci_proc_domain);/* Modify PCI: Register I/O address translation parameters */ int zpci_register_ioat (struct zpci_dev *zdev,u8 dmaas, -u64 base,u64 limit,u64 iota) +u64 base,u64 limit,u64 iota,u8 *status) {u64 req =ZPCI_CREATE_REQ (zdev->fh, dmaas,ZPCI_MOD_FC_REG_IOAT );struct zpci_fib fib = {0 }; -u8 cc, status; +u8 cc;WARN_ON_ONCE (iota &0x3fff ); fib.pba = base; fib.pal = limit; fib.iota = iota |ZPCI_IOTA_RTTO_FLAG ; fib.gd = zdev->gisa; - cc =zpci_mod_fc (req, &fib, &status); + cc =zpci_mod_fc (req, &fib, status);if (cc) -zpci_dbg (3 ,"reg ioat fid:%x, cc:%d, status:%d\n" , zdev->fid, cc, status); +zpci_dbg (3 ,"reg ioat fid:%x, cc:%d, status:%d\n" , zdev->fid, cc, *status);return cc; }EXPORT_SYMBOL_GPL (zpci_register_ioat);@@ -764,6 +764,7 @@ EXPORT_SYMBOL_GPL(zpci_disable_device);*/ int zpci_hot_reset_device (struct zpci_dev *zdev) { +u8 status;int rc;zpci_dbg (3 ,"rst fid:%x, fh:%x\n" , zdev->fid, zdev->fh);@@ -787,7 +788,7 @@ int zpci_hot_reset_device(struct zpci_dev *zdev)if (zdev->dma_table) rc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table)); +virt_to_phys (zdev->dma_table), &status);else rc =zpci_dma_init_device (zdev);if (rc) {arch/s390/pci/pci_dma.c +2
-1@@ -547,6 +547,7 @@ static void s390_dma_unmap_sg(struct device *dev, struct scatterlist *sg,int zpci_dma_init_device (struct zpci_dev *zdev) { +u8 status;int rc;/* @@ -598,7 +599,7 @@ int zpci_dma_init_device(struct zpci_dev *zdev) }if (zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (zdev->dma_table))) { +virt_to_phys (zdev->dma_table), &status)) { rc = -EIO ; goto free_bitmap; }drivers/iommu/s390-iommu.c +7
-2@@ -98,6 +98,7 @@ static int s390_iommu_attach_device(struct iommu_domain *domain,struct s390_domain *s390_domain =to_s390_domain (domain);struct zpci_dev *zdev =to_zpci_dev (dev);unsigned long flags; +u8 status;int cc;if (!zdev)@@ -113,8 +114,12 @@ static int s390_iommu_attach_device(struct iommu_domain *domain,zpci_dma_exit_device (zdev); cc =zpci_register_ioat (zdev,0 , zdev->start_dma, zdev->end_dma, -virt_to_phys (s390_domain->dma_table)); -if (cc) +virt_to_phys (s390_domain->dma_table), &status); +/* +* If the device is undergoing error recovery the reset code +* will re-establish the new domain. +*/ +if (cc && status !=ZPCI_PCI_ST_FUNC_NOT_AVAIL )return -EIO ; zdev->dma_table = s390_domain->dma_table;
Niklas Schnelle
maintainerPATCH 2/5 iommu/s390: Add I/O TLB ops
In reply to Niklas SchnelleCurrently s390-iommu does an I/O TLB flush (RPCIT) for every update of the I/O translation table explicitly. For one this is wasteful since RPCIT can be skipped after a mapping operation if zdev->tlb_refresh is unset. Moreover we can do a single RPCIT for a range of pages including whne doing lazy unmapping.
Thankfully both of these optimizations can be achieved by implementing the IOMMU operations common code provides for the different types of I/O tlb flushes:
* flush_iotlb_all: Flushes the I/O TLB for the entire IOVA space
* iotlb_sync: Flushes the I/O TLB for a range of pages that can be gathered up, for example to implement lazy unmapping.
* iotlb_sync_map: Flushes the I/O TLB after a mapping operation
--- drivers/iommu/s390-iommu.c | 76 ++++++++++++++++++++++++++++++++------ 1 file changed, 65 insertions(+), 11 deletions(-)
drivers/iommu/s390-iommu.c +65 -11
@@ -199,14 +199,72 @@ static void s390_iommu_release_device(struct device *dev)__s390_iommu_detach_device (zdev); } +static void s390_iommu_flush_iotlb_all (struct iommu_domain *domain) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , zdev->start_dma, + zdev->end_dma - zdev->start_dma +1 ); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync (struct iommu_domain *domain, +struct iommu_iotlb_gather *gather) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +size_t size = gather->end - gather->start +1 ; +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +/* If gather was never added to there is nothing to flush */ +if (gather->start ==ULONG_MAX ) +return ; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , gather->start, + size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync_map (struct iommu_domain *domain, +unsigned long iova,size_t size) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +if (!zdev->tlb_refresh) +continue ; + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , + iova, size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} +static int s390_iommu_update_trans (struct s390_domain *s390_domain,phys_addr_t pa,dma_addr_t dma_addr,unsigned long nr_pages,int flags) {phys_addr_t page_addr = pa &PAGE_MASK ; -dma_addr_t start_dma_addr = dma_addr;unsigned long irq_flags, i; -struct zpci_dev *zdev;unsigned long *entry;int rc =0 ;
@@ -225,15 +283,6 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain, dma_addr +=PAGE_SIZE ; } -spin_lock (&s390_domain->list_lock); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { - rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , - start_dma_addr, nr_pages *PAGE_SIZE ); -if (rc) -break ; - } -spin_unlock (&s390_domain->list_lock); - undo_cpu_trans:if (rc && ((flags &ZPCI_PTE_VALID_MASK ) ==ZPCI_PTE_VALID )) { flags =ZPCI_PTE_INVALID ;
@@ -340,6 +389,8 @@ static size_t s390_iommu_unmap_pages(struct iommu_domain *domain,if (rc)return 0 ; +iommu_iotlb_gather_add_range (gather, iova, size); +return size; }
@@ -384,6 +435,9 @@ static const struct iommu_ops s390_iommu_ops = { .detach_dev = s390_iommu_detach_device, .map_pages = s390_iommu_map_pages, .unmap_pages = s390_iommu_unmap_pages, + .flush_iotlb_all = s390_iommu_flush_iotlb_all, + .iotlb_sync = s390_iommu_iotlb_sync, + .iotlb_sync_map = s390_iommu_iotlb_sync_map, .iova_to_phys = s390_iommu_iova_to_phys, .free = s390_domain_free, }
Signature · 1 line
2.34.1
Matthew Rosato
maintainerRe: [PATCH 2/5] iommu/s390: Add I/O TLB ops
Quoted 47 lines · Niklas Schnelle
Currently s390-iommu does an I/O TLB flush (RPCIT) for every update of the I/O translation table explicitly. For one this is wasteful since RPCIT can be skipped after a mapping operation if
zdev->tlb_refreshis unset. Moreover we can do a single RPCIT for a range of pages including whne doing lazy unmapping.Thankfully both of these optimizations can be achieved by implementing the IOMMU operations common code provides for the different types of I/O tlb flushes:
*
flush_iotlb_all: Flushes the I/O TLB for the entire IOVA space
*iotlb_sync: Flushes the I/O TLB for a range of pages that can be gathered up, for example to implement lazy unmapping.
*iotlb_sync_map: Flushes the I/O TLB after a mapping operationSigned-off-by Niklas Schnelle <[email protected]>--- drivers/iommu/s390-iommu.c | 76 ++++++++++++++++++++++++++++++++------ 1 file changed, 65 insertions(+), 11 deletions(-)drivers/iommu/s390-iommu.c +19
-0@@ -199,14 +199,72 @@ static void s390_iommu_release_device(struct device *dev)__s390_iommu_detach_device (zdev); } +static void s390_iommu_flush_iotlb_all (struct iommu_domain *domain) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , zdev->start_dma, + zdev->end_dma - zdev->start_dma +1 ); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync (struct iommu_domain *domain, +struct iommu_iotlb_gather *gather)
drivers/iommu/s390-iommu.c static void s390_iommu_release_device(struct device *dev) · line 230
Quoted 10 lines
drivers/iommu/s390-iommu.c +10
-0+{ +struct s390_domain *s390_domain =to_s390_domain (domain); +size_t size = gather->end - gather->start +1 ; +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +/* If gather was never added to there is nothing to flush */ +if (gather->start ==ULONG_MAX ) +return ;
Hmm, this seems a little awkward in that it depends on the init value in iommu_iotlb_gather_init never changing. I don't see any other iommu drivers doing this -- Is there no other way to tell there's nothing to flush?
If we really need to do this, maybe some shared #define in iommu.h that is used in iommu_iotlb_gather_init and here?
Quoted 77 lines
drivers/iommu/s390-iommu.c +36
-11+ +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , gather->start, + size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync_map (struct iommu_domain *domain, +unsigned long iova,size_t size) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +if (!zdev->tlb_refresh) +continue ; + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , + iova, size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} +static int s390_iommu_update_trans (struct s390_domain *s390_domain,phys_addr_t pa,dma_addr_t dma_addr,unsigned long nr_pages,int flags) {phys_addr_t page_addr = pa &PAGE_MASK ; -dma_addr_t start_dma_addr = dma_addr;unsigned long irq_flags, i; -struct zpci_dev *zdev;unsigned long *entry;int rc =0 ;@@ -225,15 +283,6 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain, dma_addr +=PAGE_SIZE ; } -spin_lock (&s390_domain->list_lock); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { - rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , - start_dma_addr, nr_pages *PAGE_SIZE ); -if (rc) -break ; - } -spin_unlock (&s390_domain->list_lock); - undo_cpu_trans:if (rc && ((flags &ZPCI_PTE_VALID_MASK ) ==ZPCI_PTE_VALID )) { flags =ZPCI_PTE_INVALID ;@@ -340,6 +389,8 @@ static size_t s390_iommu_unmap_pages(struct iommu_domain *domain,if (rc)return 0 ; +iommu_iotlb_gather_add_range (gather, iova, size); +return size; }@@ -384,6 +435,9 @@ static const struct iommu_ops s390_iommu_ops = { .detach_dev = s390_iommu_detach_device, .map_pages = s390_iommu_map_pages, .unmap_pages = s390_iommu_unmap_pages, + .flush_iotlb_all = s390_iommu_flush_iotlb_all, + .iotlb_sync = s390_iommu_iotlb_sync, + .iotlb_sync_map = s390_iommu_iotlb_sync_map, .iova_to_phys = s390_iommu_iova_to_phys, .free = s390_domain_free, }
Robin Murphy
reviewerRe: [PATCH 2/5] iommu/s390: Add I/O TLB ops
Quoted 61 lines · Matthew Rosato
Quoted 47 lines · Niklas Schnelle
Currently s390-iommu does an I/O TLB flush (RPCIT) for every update of the I/O translation table explicitly. For one this is wasteful since RPCIT can be skipped after a mapping operation if
zdev->tlb_refreshis unset. Moreover we can do a single RPCIT for a range of pages including whne doing lazy unmapping.Thankfully both of these optimizations can be achieved by implementing the IOMMU operations common code provides for the different types of I/O tlb flushes:
*
flush_iotlb_all: Flushes the I/O TLB for the entire IOVA space
*iotlb_sync: Flushes the I/O TLB for a range of pages that can be gathered up, for example to implement lazy unmapping.
*iotlb_sync_map: Flushes the I/O TLB after a mapping operationSigned-off-by Niklas Schnelle <[email protected]>--- drivers/iommu/s390-iommu.c | 76 ++++++++++++++++++++++++++++++++------ 1 file changed, 65 insertions(+), 11 deletions(-)drivers/iommu/s390-iommu.c +19
-0@@ -199,14 +199,72 @@ static void s390_iommu_release_device(struct device *dev)__s390_iommu_detach_device (zdev); } +static void s390_iommu_flush_iotlb_all (struct iommu_domain *domain) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , zdev->start_dma, + zdev->end_dma - zdev->start_dma +1 ); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync (struct iommu_domain *domain, +struct iommu_iotlb_gather *gather)drivers/iommu/s390-iommu.c static void s390_iommu_release_device(struct device *dev) · line 230
Quoted 10 lines
drivers/iommu/s390-iommu.c +10
-0+{ +struct s390_domain *s390_domain =to_s390_domain (domain); +size_t size = gather->end - gather->start +1 ; +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +/* If gather was never added to there is nothing to flush */ +if (gather->start ==ULONG_MAX ) +return ;Hmm, this seems a little awkward in that it depends on the init value in
iommu_iotlb_gather_initnever changing. I don't see any other iommu drivers doing this -- Is there no other way to tell there's nothing to flush?
Quoted 1 line
If we really need to do this, maybe some shared #define in
iommu.hthat is used iniommu_iotlb_gather_initand here?
If you can trust yourselves to never gather a single byte (which by construction should be impossible), "!gather->end" is perhaps a tiny bit more robust (and consistent with iommu_iotlb_gather_is_disjoint()), although given the way that iommu_iotlb_gather_add_*() work I don't think either initial value has much chance of changing in practice, short of some larger refactoring that would likely have to touch all the users anyway. If you still want to be as foolproof as possible, using "gather->start > gather->end" would represent the most general form of the initial conditions.
FWIW, SMMUv3 does also check for an empty range, but using gather->pgsize that is only relevant with add_page(). The other gather users seem happy to go ahead and just issue whatever wacky invalidation command those initial values end up looking like. I think an empty sync should really only happen in unexpected conditions like an unmap failing, so it shouldn't be a case that deserves a great deal of optimisation effort.
Thanks,
Robin.
Quoted 78 lines
Quoted 77 lines
drivers/iommu/s390-iommu.c +36
-11+ +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , gather->start, + size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync_map (struct iommu_domain *domain, +unsigned long iova,size_t size) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +if (!zdev->tlb_refresh) +continue ; + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , + iova, size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} +static int s390_iommu_update_trans (struct s390_domain *s390_domain,phys_addr_t pa,dma_addr_t dma_addr,unsigned long nr_pages,int flags) {phys_addr_t page_addr = pa &PAGE_MASK ; -dma_addr_t start_dma_addr = dma_addr;unsigned long irq_flags, i; -struct zpci_dev *zdev;unsigned long *entry;int rc =0 ;@@ -225,15 +283,6 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain, dma_addr +=PAGE_SIZE ; } -spin_lock (&s390_domain->list_lock); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { - rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , - start_dma_addr, nr_pages *PAGE_SIZE ); -if (rc) -break ; - } -spin_unlock (&s390_domain->list_lock); - undo_cpu_trans:if (rc && ((flags &ZPCI_PTE_VALID_MASK ) ==ZPCI_PTE_VALID )) { flags =ZPCI_PTE_INVALID ;@@ -340,6 +389,8 @@ static size_t s390_iommu_unmap_pages(struct iommu_domain *domain,if (rc)return 0 ; +iommu_iotlb_gather_add_range (gather, iova, size); +return size; }@@ -384,6 +435,9 @@ static const struct iommu_ops s390_iommu_ops = { .detach_dev = s390_iommu_detach_device, .map_pages = s390_iommu_map_pages, .unmap_pages = s390_iommu_unmap_pages, + .flush_iotlb_all = s390_iommu_flush_iotlb_all, + .iotlb_sync = s390_iommu_iotlb_sync, + .iotlb_sync_map = s390_iommu_iotlb_sync_map, .iova_to_phys = s390_iommu_iova_to_phys, .free = s390_domain_free, }
Niklas Schnelle
maintainerRe: [PATCH 2/5] iommu/s390: Add I/O TLB ops
Quoted 82 lines · Robin Murphy
Quoted 61 lines · Matthew Rosato
Quoted 47 lines · Niklas Schnelle
Currently s390-iommu does an I/O TLB flush (RPCIT) for every update of the I/O translation table explicitly. For one this is wasteful since RPCIT can be skipped after a mapping operation if
zdev->tlb_refreshis unset. Moreover we can do a single RPCIT for a range of pages including whne doing lazy unmapping.Thankfully both of these optimizations can be achieved by implementing the IOMMU operations common code provides for the different types of I/O tlb flushes:
*
flush_iotlb_all: Flushes the I/O TLB for the entire IOVA space
*iotlb_sync: Flushes the I/O TLB for a range of pages that can be gathered up, for example to implement lazy unmapping.
*iotlb_sync_map: Flushes the I/O TLB after a mapping operationSigned-off-by Niklas Schnelle <[email protected]>--- drivers/iommu/s390-iommu.c | 76 ++++++++++++++++++++++++++++++++------ 1 file changed, 65 insertions(+), 11 deletions(-)drivers/iommu/s390-iommu.c +19
-0@@ -199,14 +199,72 @@ static void s390_iommu_release_device(struct device *dev)__s390_iommu_detach_device (zdev); } +static void s390_iommu_flush_iotlb_all (struct iommu_domain *domain) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , zdev->start_dma, + zdev->end_dma - zdev->start_dma +1 ); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync (struct iommu_domain *domain, +struct iommu_iotlb_gather *gather)drivers/iommu/s390-iommu.c static void s390_iommu_release_device(struct device *dev) · line 230
Quoted 10 lines
drivers/iommu/s390-iommu.c +10
-0+{ +struct s390_domain *s390_domain =to_s390_domain (domain); +size_t size = gather->end - gather->start +1 ; +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +/* If gather was never added to there is nothing to flush */ +if (gather->start ==ULONG_MAX ) +return ;Hmm, this seems a little awkward in that it depends on the init value in
iommu_iotlb_gather_initnever changing. I don't see any other iommu drivers doing this -- Is there no other way to tell there's nothing to flush?Quoted 1 line
If we really need to do this, maybe some shared #define in
iommu.hthat is used iniommu_iotlb_gather_initand here?If you can trust yourselves to never gather a single byte (which by construction should be impossible), "!gather->end" is perhaps a tiny bit more robust (and consistent with
iommu_iotlb_gather_is_disjoint()), although given the way that iommu_iotlb_gather_add_*() work I don't think either initial value has much chance of changing in practice, short of some larger refactoring that would likely have to touch all the users anyway. If you still want to be as foolproof as possible, using "gather->start>gather->end" would represent the most general form of the initial conditions.FWIW, SMMUv3 does also check for an empty range, but using
gather->pgsizethat is only relevant withadd_page(). The other gather users seem happy to go ahead and just issue whatever wacky invalidation command those initial values end up looking like. I think an empty sync should really only happen in unexpected conditions like an unmap failing, so it shouldn't be a case that deserves a great deal of optimisation effort.
Quoted 3 lines
Thanks,
Robin.
Yeah I agree this should only happen when unmap failed. I think I added this when I was playing around with adding an intermediate flush similar to what amd_iommu_iotlb_gather_add_page() does, only that in some intermediate stages I could end up with nothing left to flush. That whole optimization did turn out not to help and I removed it again. I think even if it's only for the error case now, I'd like to keep it though. This makes sure we don't get weirdly sized flushes in the error case. I'll use '!gather->end' to be consistent with iommu_iotlb_gather_is_disjoint() as you suggested.
Speaking of that AMD optimization, I'm actually not sure that it does the right thing for AMD either. The way I read the code, it does more but only contiguous TLB flushes in virtualized mode and at least for us this turned out detrimental. Also the comment, at least to me, makes it sound as if they were trying for fewer flushes but it's worded a bit confusingly so not sure.
Thanks,
Niklas
Quoted 77 lines
Quoted 77 lines
Quoted 77 lines
drivers/iommu/s390-iommu.c +36
-11+ +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , gather->start, + size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} + +static void s390_iommu_iotlb_sync_map (struct iommu_domain *domain, +unsigned long iova,size_t size) +{ +struct s390_domain *s390_domain =to_s390_domain (domain); +struct zpci_dev *zdev; +unsigned long flags; +int rc; + +spin_lock_irqsave (&s390_domain->list_lock, flags); +list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +if (!zdev->tlb_refresh) +continue ; + rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , + iova, size); +if (rc) +break ; + } +spin_unlock_irqrestore (&s390_domain->list_lock, flags); +} +static int s390_iommu_update_trans (struct s390_domain *s390_domain,phys_addr_t pa,dma_addr_t dma_addr,unsigned long nr_pages,int flags) {phys_addr_t page_addr = pa &PAGE_MASK ; -dma_addr_t start_dma_addr = dma_addr;unsigned long irq_flags, i; -struct zpci_dev *zdev;unsigned long *entry;int rc =0 ;@@ -225,15 +283,6 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain, dma_addr +=PAGE_SIZE ; } -spin_lock (&s390_domain->list_lock); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { - rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , - start_dma_addr, nr_pages *PAGE_SIZE ); -if (rc) -break ; - } -spin_unlock (&s390_domain->list_lock); - undo_cpu_trans:if (rc && ((flags &ZPCI_PTE_VALID_MASK ) ==ZPCI_PTE_VALID )) { flags =ZPCI_PTE_INVALID ;@@ -340,6 +389,8 @@ static size_t s390_iommu_unmap_pages(struct iommu_domain *domain,if (rc)return 0 ; +iommu_iotlb_gather_add_range (gather, iova, size); +return size; }@@ -384,6 +435,9 @@ static const struct iommu_ops s390_iommu_ops = { .detach_dev = s390_iommu_detach_device, .map_pages = s390_iommu_map_pages, .unmap_pages = s390_iommu_unmap_pages, + .flush_iotlb_all = s390_iommu_flush_iotlb_all, + .iotlb_sync = s390_iommu_iotlb_sync, + .iotlb_sync_map = s390_iommu_iotlb_sync_map, .iova_to_phys = s390_iommu_iova_to_phys, .free = s390_domain_free, }
Niklas Schnelle
maintainerPATCH 3/5 iommu/s390: Use RCU to allow concurrent domain_list iteration
In reply to Niklas SchnelleThe s390_domain->devices list is only added to when new devices are attached but is iterated through in read-only fashion for every mapping operation as well as for I/O TLB flushes and thus in performance critical code causing contention on the s390_domain->list_lock. Fortunately such a read-mostly linked list is a standard use case for RCU. This change closely follows the example fpr RCU protected list given in Documentation/RCU/listRCU.rst.
--- arch/s390/include/asm/pci.h | 1 + arch/s390/pci/pci.c | 2 +- drivers/iommu/s390-iommu.c | 31 ++++++++++++++++--------------- 3 files changed, 18 insertions(+), 16 deletions(-)
arch/s390/include/asm/pci.h +1 -0
@@ -119,6 +119,7 @@ struct zpci_dev {struct list_head entry;/* list of all zpci_devices, needed for hotplug, etc. */ struct list_head iommu_list;struct kref kref; +struct rcu_head rcu;struct hotplug_slot hotplug_slot;enum zpci_state state;
arch/s390/pci/pci.c +1 -1
@@ -996,7 +996,7 @@ void zpci_release_device(struct kref *kref)break ; }zpci_dbg (3 ,"rem fid:%x\n" , zdev->fid); -kfree (zdev); +kfree_rcu (zdev, rcu); } int zpci_report_error(struct pci_dev *pdev,
drivers/iommu/s390-iommu.c +16 -15
@@ -10,6 +10,8 @@#include <linux/iommu.h> #include <linux/iommu-helper.h> #include <linux/sizes.h> +#include <linux/rculist.h> +#include <linux/rcupdate.h> #include <asm/pci_dma.h> static const struct iommu_ops s390_iommu_ops;
@@ -61,7 +63,7 @@ static struct iommu_domain *s390_domain_alloc(unsigned domain_type)spin_lock_init (&s390_domain->dma_table_lock);spin_lock_init (&s390_domain->list_lock); -INIT_LIST_HEAD (&s390_domain->devices); +INIT_LIST_HEAD_RCU (&s390_domain->devices);return &s390_domain->domain; }
@@ -70,7 +72,9 @@ static void s390_domain_free(struct iommu_domain *domain) {struct s390_domain *s390_domain =to_s390_domain (domain); +rcu_read_lock ();WARN_ON (!list_empty (&s390_domain->devices)); +rcu_read_unlock ();dma_cleanup_tables (s390_domain->dma_table);kfree (s390_domain); }
@@ -84,7 +88,7 @@ static void __s390_iommu_detach_device(struct zpci_dev *zdev)return ;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_del_init (&zdev->iommu_list); +list_del_rcu (&zdev->iommu_list);spin_unlock_irqrestore (&s390_domain->list_lock, flags);zpci_unregister_ioat (zdev,0 );
@@ -127,7 +131,7 @@ static int s390_iommu_attach_device(struct iommu_domain *domain, zdev->s390_domain = s390_domain;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_add (&zdev->iommu_list, &s390_domain->devices); +list_add_rcu (&zdev->iommu_list, &s390_domain->devices);spin_unlock_irqrestore (&s390_domain->list_lock, flags);return 0 ;
@@ -203,17 +207,16 @@ static void s390_iommu_flush_iotlb_all(struct iommu_domain *domain) {struct s390_domain *s390_domain =to_s390_domain (domain);struct zpci_dev *zdev; -unsigned long flags;int rc; -spin_lock_irqsave (&s390_domain->list_lock, flags); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +rcu_read_lock (); +list_for_each_entry_rcu (zdev, &s390_domain->devices, iommu_list) { rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , zdev->start_dma, zdev->end_dma - zdev->start_dma +1 );if (rc)break ; } -spin_unlock_irqrestore (&s390_domain->list_lock, flags); +rcu_read_unlock (); } static void s390_iommu_iotlb_sync(struct iommu_domain *domain,
@@ -222,21 +225,20 @@ static void s390_iommu_iotlb_sync(struct iommu_domain *domain,struct s390_domain *s390_domain =to_s390_domain (domain);size_t size = gather->end - gather->start +1 ;struct zpci_dev *zdev; -unsigned long flags;int rc;/* If gather was never added to there is nothing to flush */ if (gather->start ==ULONG_MAX )return ; -spin_lock_irqsave (&s390_domain->list_lock, flags); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +rcu_read_lock (); +list_for_each_entry_rcu (zdev, &s390_domain->devices, iommu_list) { rc =zpci_refresh_trans ((u64 )zdev->fh <<32 , gather->start, size);if (rc)break ; } -spin_unlock_irqrestore (&s390_domain->list_lock, flags); +rcu_read_unlock (); } static void s390_iommu_iotlb_sync_map(struct iommu_domain *domain,
@@ -244,11 +246,10 @@ static void s390_iommu_iotlb_sync_map(struct iommu_domain *domain, {struct s390_domain *s390_domain =to_s390_domain (domain);struct zpci_dev *zdev; -unsigned long flags;int rc; -spin_lock_irqsave (&s390_domain->list_lock, flags); -list_for_each_entry (zdev, &s390_domain->devices, iommu_list) { +rcu_read_lock (); +list_for_each_entry_rcu (zdev, &s390_domain->devices, iommu_list) {if (!zdev->tlb_refresh)continue ; rc = zpci_refresh_trans((u64)zdev->fh << 32,
@@ -256,7 +257,7 @@ static void s390_iommu_iotlb_sync_map(struct iommu_domain *domain,if (rc)break ; } -spin_unlock_irqrestore (&s390_domain->list_lock, flags); +rcu_read_unlock (); } static int s390_iommu_update_trans(struct s390_domain *s390_domain,
Signature · 1 line
2.34.1
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
drivers/iommu/s390-iommu.c static void __s390_iommu_detach_device(struct zpci_dev *zdev) · line 92
Quoted 7 lines · Niklas Schnelle
drivers/iommu/s390-iommu.c +1
-1@@ -84,7 +88,7 @@ static void __s390_iommu_detach_device(struct zpci_dev *zdev)return ;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_del_init (&zdev->iommu_list); +list_del_rcu (&zdev->iommu_list);spin_unlock_irqrestore (&s390_domain->list_lock, flags);
This doesn't seem obviously OK, the next steps remove the translation while we can still have concurrent RCU protected flushes going on.
Is it OK to call the flushes when after the zpci_dma_exit_device()/etc?
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 13 lines · Jason Gunthorpe
drivers/iommu/s390-iommu.c static void __s390_iommu_detach_device(struct zpci_dev *zdev) · line 92
Quoted 7 lines · Niklas Schnelle
drivers/iommu/s390-iommu.c +1
-1@@ -84,7 +88,7 @@ static void __s390_iommu_detach_device(struct zpci_dev *zdev)return ;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_del_init (&zdev->iommu_list); +list_del_rcu (&zdev->iommu_list);spin_unlock_irqrestore (&s390_domain->list_lock, flags);This doesn't seem obviously OK, the next steps remove the translation while we can still have concurrent RCU protected flushes going on.
Quoted 3 lines
Is it OK to call the flushes when after the zpci_dma_exit_device()/etc?
Jason
Interesting point. So for the flushes themselves this should be fine, once the zpci_unregister_ioat() is executed all subsequent and ongoing IOTLB flushes should return an error code without further adverse effects. Though I think we do still have an issue in the IOTLB ops for this case as that error would skip the IOTLB flushes of other attached devices.
The bigger question and that seems independent from RCU is how/if detach is supposed to work if there are still DMAs ongoing. Once we do the zpci_unregister_ioat() any DMA request coming from the PCI device will be blocked and will lead to the PCI device being isolated (put into an error state) for attempting an invalid DMA. So I had expected that calls of detach/attach would happen without expected ongoing DMAs and thus IOTLB flushes? Of course we should be robust against violations of that and unexpected DMAs for which I think isolating the PCI device is the correct response. What am I missing?
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 16 lines · Niklas Schnelle
Quoted 15 lines · Jason Gunthorpe
drivers/iommu/s390-iommu.c static void __s390_iommu_detach_device(struct zpci_dev *zdev) · line 92
Quoted 7 lines · Niklas Schnelle
drivers/iommu/s390-iommu.c +1
-1@@ -84,7 +88,7 @@ static void __s390_iommu_detach_device(struct zpci_dev *zdev)return ;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_del_init (&zdev->iommu_list); +list_del_rcu (&zdev->iommu_list);spin_unlock_irqrestore (&s390_domain->list_lock, flags);This doesn't seem obviously OK, the next steps remove the translation while we can still have concurrent RCU protected flushes going on.
Is it OK to call the flushes when after the zpci_dma_exit_device()/etc?
Quoted 8 lines
Quoted 1 line
Jason
Interesting point. So for the flushes themselves this should be fine, once the
zpci_unregister_ioat()is executed all subsequent and ongoing IOTLB flushes should return an error code without further adverse effects. Though I think we do still have an issue in the IOTLB ops for this case as that error would skip the IOTLB flushes of other attached devices.
That sounds bad
Quoted 7 lines
The bigger question and that seems independent from RCU is how/if detach is supposed to work if there are still DMAs ongoing. Once we do the
zpci_unregister_ioat()any DMA request coming from the PCI device will be blocked and will lead to the PCI device being isolated (put into an error state) for attempting an invalid DMA. So I had expected that calls of detach/attach would happen without expected ongoing DMAs and thus IOTLB flushes?
"ongoing DMA" from this device shouuld be stopped, it doesn't mean that the other devices attached to the same domain are not also still operating and also still having flushes. So now that it is RCU a flush triggered by a different device will continue to see this now disabled device and try to flush it until the grace period.
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 19 lines · Jason Gunthorpe
Quoted 18 lines · Niklas Schnelle
Quoted 16 lines · Jason Gunthorpe
drivers/iommu/s390-iommu.c static void __s390_iommu_detach_device(struct zpci_dev *zdev) · line 92
Quoted 7 lines · Niklas Schnelle
drivers/iommu/s390-iommu.c +1
-1@@ -84,7 +88,7 @@ static void __s390_iommu_detach_device(struct zpci_dev *zdev)return ;spin_lock_irqsave (&s390_domain->list_lock, flags); -list_del_init (&zdev->iommu_list); +list_del_rcu (&zdev->iommu_list);spin_unlock_irqrestore (&s390_domain->list_lock, flags);This doesn't seem obviously OK, the next steps remove the translation while we can still have concurrent RCU protected flushes going on.
Is it OK to call the flushes when after the zpci_dma_exit_device()/etc?
Jason
Quoted 8 lines
Quoted 6 lines
Interesting point. So for the flushes themselves this should be fine, once the
zpci_unregister_ioat()is executed all subsequent and ongoing IOTLB flushes should return an error code without further adverse effects. Though I think we do still have an issue in the IOTLB ops for this case as that error would skip the IOTLB flushes of other attached devices.That sounds bad
Thankfully it's very easy to fix since our IOTLB flushes are per PCI function, I just need to continue the loop in the IOTLB ops on error instead of breaking out of it and skipping the other devices. Makes no sense anyway to skip devices just because there is an error on another device.
Quoted 10 lines
Quoted 9 lines
The bigger question and that seems independent from RCU is how/if detach is supposed to work if there are still DMAs ongoing. Once we do the
zpci_unregister_ioat()any DMA request coming from the PCI device will be blocked and will lead to the PCI device being isolated (put into an error state) for attempting an invalid DMA. So I had expected that calls of detach/attach would happen without expected ongoing DMAs and thus IOTLB flushes?
Quoted 7 lines
"ongoing DMA" from this device shouuld be stopped, it doesn't mean that the other devices attached to the same domain are not also still operating and also still having flushes. So now that it is RCU a flush triggered by a different device will continue to see this now disabled device and try to flush it until the grace period.
Jason
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use call_rcu() to do the zpci_unregister_ioat() but I'm not sure how to then make sure that a subsequent zpci_register_ioat() only happens after that without adding too much more logic.
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.
This won't work either as the domain could have been freed before the call_rcu() happens, the domain needs to be detached synchronously
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent zpci_register_ioat(). What about the obvious one. Just call synchronize_rcu() before zpci_unregister_ioat()?
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 11 lines · Niklas Schnelle
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.
Quoted 8 lines
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent
zpci_register_ioat(). What about the obvious one. Just callsynchronize_rcu()beforezpci_unregister_ioat()?
Ah, it can be done, but be prepared to wait >> 1s for synchronize_rcu to complete in some cases.
What you have seems like it could be OK, just deal with the ugly racy failure
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 21 lines · Jason Gunthorpe
Quoted 11 lines · Niklas Schnelle
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.Quoted 8 lines
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent
zpci_register_ioat(). What about the obvious one. Just callsynchronize_rcu()beforezpci_unregister_ioat()?
Quoted 7 lines
Ah, it can be done, but be prepared to wait >> 1s for
synchronize_rcuto complete in some cases.What you have seems like it could be OK, just deal with the ugly racy failure
Jason
I'd tend to go with synchronize_rcu(). It won't leave us with spurious error logs for the failed IOTLB flushes and as you said one expects detach to be synchronous. I don't think waiting in it will be a problem. But this is definitely something you're more of an expert on so I'll trust your judgement. Looking at other callers of synchronize_rcu() quite a few of them look to be in similar detach/release kind of situations though not sure how frequent and performance critical IOMMU domain detaching is in comparison.
Thanks,
Niklas
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 30 lines · Niklas Schnelle
Quoted 21 lines · Jason Gunthorpe
Quoted 11 lines · Niklas Schnelle
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.Quoted 8 lines
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent
zpci_register_ioat(). What about the obvious one. Just callsynchronize_rcu()beforezpci_unregister_ioat()?Quoted 7 lines
Ah, it can be done, but be prepared to wait >> 1s for
synchronize_rcuto complete in some cases.What you have seems like it could be OK, just deal with the ugly racy failure
Jason
Quoted 8 lines
I'd tend to go with
synchronize_rcu(). It won't leave us with spurious error logs for the failed IOTLB flushes and as you said one expects detach to be synchronous. I don't think waiting in it will be a problem. But this is definitely something you're more of an expert on so I'll trust your judgement. Looking at other callers ofsynchronize_rcu()quite a few of them look to be in similar detach/release kind of situations though not sure how frequent and performance critical IOMMU domain detaching is in comparison.
I would not do it on domain detaching, that is something triggered by userspace through VFIO and it could theoritically happen alot, eg in vIOMMU scenarios.
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 40 lines · Jason Gunthorpe
Quoted 30 lines · Niklas Schnelle
Quoted 21 lines · Jason Gunthorpe
Quoted 11 lines · Niklas Schnelle
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.Quoted 8 lines
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent
zpci_register_ioat(). What about the obvious one. Just callsynchronize_rcu()beforezpci_unregister_ioat()?Quoted 7 lines
Ah, it can be done, but be prepared to wait >> 1s for
synchronize_rcuto complete in some cases.What you have seems like it could be OK, just deal with the ugly racy failure
Jason
Quoted 8 lines
I'd tend to go with
synchronize_rcu(). It won't leave us with spurious error logs for the failed IOTLB flushes and as you said one expects detach to be synchronous. I don't think waiting in it will be a problem. But this is definitely something you're more of an expert on so I'll trust your judgement. Looking at other callers ofsynchronize_rcu()quite a few of them look to be in similar detach/release kind of situations though not sure how frequent and performance critical IOMMU domain detaching is in comparison.
Quoted 5 lines
I would not do it on domain detaching, that is something triggered by userspace through VFIO and it could theoritically happen alot, eg in vIOMMU scenarios.
Jason
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly synchronize_rcu() should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand the synchronize_rcu() comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does a synchronize_rcu() and can be triggered from user-space too.
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.
Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.
Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a close() system call. Generally it should be weighed carefully
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 16 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.
Quoted 7 lines
Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a
close()system call. Generally it should be weighed carefullyJason
Thanks for the detailed explanation. Then let's not put a synchronize_rcu() in detach, as I said as long as the I/O translation tables are there an IOTLB flush after zpci_unregister_ioat() should result in an ignorable error. That said, I think if we don't have the synchronize_rcu() in detach we need it in s390_domain_free() before freeing the I/O translation tables.
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 23 lines · Niklas Schnelle
Quoted 22 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a
close()system call. Generally it should be weighed carefully
Quoted 8 lines
Quoted 1 line
Jason
Thanks for the detailed explanation. Then let's not put a
synchronize_rcu()in detach, as I said as long as the I/O translation tables are there an IOTLB flush afterzpci_unregister_ioat()should result in an ignorable error. That said, I think if we don't have thesynchronize_rcu()in detach we need it ins390_domain_free()before freeing the I/O translation tables.
Yes, it would be appropriate to free those using one of the rcu free'rs, (eg kfree_rcu) not synchronize_rcu()
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 33 lines · Jason Gunthorpe
Quoted 23 lines · Niklas Schnelle
Quoted 22 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a
close()system call. Generally it should be weighed carefullyQuoted 8 lines
Quoted 1 line
Jason
Thanks for the detailed explanation. Then let's not put a
synchronize_rcu()in detach, as I said as long as the I/O translation tables are there an IOTLB flush afterzpci_unregister_ioat()should result in an ignorable error. That said, I think if we don't have thesynchronize_rcu()in detach we need it ins390_domain_free()before freeing the I/O translation tables.
Quoted 4 lines
Yes, it would be appropriate to free those using one of the rcu free'rs, (eg
kfree_rcu) notsynchronize_rcu()Jason
They are allocated via kmem_cache_alloc() from caches shared by all IOMMU's so can't use kfree_rcu() directly. Also we're only freeing the entire I/O translation table of one IOMMU at once after it is not used anymore. Before that it is only grown. So I think synchronize_rcu() is the obvious and simple choice since we only need one grace period.
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 37 lines · Niklas Schnelle
Quoted 36 lines · Jason Gunthorpe
Quoted 23 lines · Niklas Schnelle
Quoted 22 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a
close()system call. Generally it should be weighed carefullyQuoted 8 lines
Quoted 1 line
Jason
Thanks for the detailed explanation. Then let's not put a
synchronize_rcu()in detach, as I said as long as the I/O translation tables are there an IOTLB flush afterzpci_unregister_ioat()should result in an ignorable error. That said, I think if we don't have thesynchronize_rcu()in detach we need it ins390_domain_free()before freeing the I/O translation tables.Yes, it would be appropriate to free those using one of the rcu free'rs, (eg
kfree_rcu) notsynchronize_rcu()
Quoted 7 lines
Quoted 1 line
Jason
They are allocated via
kmem_cache_alloc()from caches shared by all IOMMU's so can't usekfree_rcu()directly. Also we're only freeing the entire I/O translation table of one IOMMU at once after it is not used anymore. Before that it is only grown. So I thinksynchronize_rcu()is the obvious and simple choice since we only need one grace period.
It has the same issue as doing it for the other reason, adding synchronize_rcu() to the domain free path is undesirable.
The best thing is to do as kfree_rcu() does now, basically:
rcu_head = kzalloc(rcu_head, GFP_NOWAIT, GFP_NOWARN) if (!rcu_head)
synchronize_rcu()
else
call_rcu(rcu_head)
And then call kmem_cache_free() from the rcu callback
But this is getting very complicated, you might be better to refcount the domain itself and acquire the refcount under RCU. This turns the locking problem into a per-domain-object lock instead of a global lock which is usually good enough and simpler to understand.
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 51 lines · Jason Gunthorpe
Quoted 37 lines · Niklas Schnelle
Quoted 36 lines · Jason Gunthorpe
Quoted 23 lines · Niklas Schnelle
Quoted 22 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Thanks for the explanation, still would like to grok this a bit more if you don't mind. If I do read things correctly
synchronize_rcu()should run in the conext of the VFIO ioctl in this case and shouldn't block anything else in the kernel, correct? At least that's how I understand thesynchronize_rcu()comments and the fact that e.g. net/vmw_vsock/virtio_transport.c:virtio_vsock_remove() also does asynchronize_rcu()and can be triggered from user-space too.Yes, but I wouldn't look in the kernel to understand if things are OK
Quoted 3 lines
So we're
more worried about user-space getting slowed down rather than a Denial- of-Service against other kernel tasks.Yes, functionally it is OK, but for something like vfio with vIOMMU you could be looking at several domains that have to be detached sequentially and with grace periods > 1s you can reach multiple seconds to complete something like a
close()system call. Generally it should be weighed carefullyQuoted 8 lines
Quoted 1 line
Jason
Thanks for the detailed explanation. Then let's not put a
synchronize_rcu()in detach, as I said as long as the I/O translation tables are there an IOTLB flush afterzpci_unregister_ioat()should result in an ignorable error. That said, I think if we don't have thesynchronize_rcu()in detach we need it ins390_domain_free()before freeing the I/O translation tables.Yes, it would be appropriate to free those using one of the rcu free'rs, (eg
kfree_rcu) notsynchronize_rcu()Quoted 7 lines
Quoted 1 line
Jason
They are allocated via
kmem_cache_alloc()from caches shared by all IOMMU's so can't usekfree_rcu()directly. Also we're only freeing the entire I/O translation table of one IOMMU at once after it is not used anymore. Before that it is only grown. So I thinksynchronize_rcu()is the obvious and simple choice since we only need one grace period.It has the same issue as doing it for the other reason, adding
synchronize_rcu()to the domain free path is undesirable.The best thing is to do as
kfree_rcu()does now, basically:
Quoted 7 lines
rcu_head=kzalloc(rcu_head, GFP_NOWAIT, GFP_NOWARN)if (!rcu_head)
synchronize_rcu()
else
call_rcu(rcu_head)And then call
kmem_cache_free()from the rcu callback
Hmm, maybe a stupid question but why can't I just put the rcu_head in struct s390_domain and then do a call_rcu() on that with a callback that does:
dma_cleanup_tables(s390_domain->dma_table); kfree(s390_domain);
I.e. the rest of the current s390_domain_free().
Then I don't have to worry about failing to allocate the rcu_head and it's simple enough. Basically just do the actual freeing of the s390_domain via call_rcu().
Quoted 7 lines
But this is getting very complicated, you might be better to refcount the domain itself and acquire the refcount under RCU. This turns the locking problem into a per-domain-object lock instead of a global lock which is usually good enough and simpler to understand.
Jason
Sorry I might be a bit slow as I'm new to RCU but I don't understand this yet, especially the last part. Before this patch we do have a per- domain lock but I'm sure that's not the kind of "per-domain-object lock" you're talking about or else we wouldn't need RCU at all. Is this maybe a different way of expressing the above idea using the analogy with reference counting from whatisRCU.rst? Meaning we treat the fact that there may still be RCU readers as "there are still references to s390_domain"?
Or do you mean to use a kref that is taken by RCU readers together with rcu_read_lock() and dropped at rcu_read_unlock() such that during the RCU read critical sections the refcount can't fall below 1 and the domain is actually freed once we have a) put the initial reference during s390_domain_free() and b) put all temporary references on exiting the RCU read critical sections?
Re: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
Quoted 12 lines · Niklas Schnelle
Quoted 7 lines
rcu_head=kzalloc(rcu_head, GFP_NOWAIT, GFP_NOWARN)if (!rcu_head)
synchronize_rcu()
else
call_rcu(rcu_head)And then call
kmem_cache_free()from the rcu callbackHmm, maybe a stupid question but why can't I just put the
rcu_headin structs390_domainand then do acall_rcu()on that with a callback that does:
Quoted 7 lines
dma_cleanup_tables(s390_domain->dma_table); kfree(s390_domain);I.e. the rest of the current
s390_domain_free().
Then I don't have to worry about failing to allocate thercu_headand it's simple enough. Basically just do the actual freeing of thes390_domainviacall_rcu().
Oh, if you never reallocate the dma_table then yes that is a good idea
Quoted 6 lines
Or do you mean to use a kref that is taken by RCU readers together with
rcu_read_lock()and dropped atrcu_read_unlock()such that during the RCU read critical sections the refcount can't fall below 1 and the domain is actually freed once we have a) put the initial reference durings390_domain_free()and b) put all temporary references on exiting the RCU read critical sections?
Yes, this is a common pattern. Usually you want to optimize away the global lock that protects, say, a linked list and then accept a local lock/refcount inside the object
Jason
Niklas Schnelle
maintainerRe: [PATCH 3/5] iommu/s390: Use RCU to allow concurrent domain_list iteration
In reply to Niklas SchnelleQuoted 39 lines · Niklas Schnelle
Quoted 21 lines · Jason Gunthorpe
Quoted 11 lines · Niklas Schnelle
Quoted 10 lines · Jason Gunthorpe
Quoted 7 lines · Niklas Schnelle
Ok that makes sense thanks for the explanation. So yes my assessment is still that in this situation the IOTLB flush is architected to return an error that we can ignore. Not the most elegant I admit but at least it's simple. Alternatively I guess we could use
call_rcu()to do thezpci_unregister_ioat()but I'm not sure how to then make sure that a subsequentzpci_register_ioat()only happens after that without adding too much more logic.Quoted 8 lines
Quoted 4 lines
This won't work either as the domain could have been freed before the
call_rcu()happens, the domain needs to be detached synchronouslyJason
Yeah right, that is basically the same issue I was thinking of for a subsequent
zpci_register_ioat(). What about the obvious one. Just callsynchronize_rcu()beforezpci_unregister_ioat()?Quoted 7 lines
Ah, it can be done, but be prepared to wait >> 1s for
synchronize_rcuto complete in some cases.What you have seems like it could be OK, just deal with the ugly racy failure
Jason
I'd tend to go with
synchronize_rcu(). It won't leave us with spurious error logs for the failed IOTLB flushes and as you said one expects detach to be synchronous. I don't think waiting in it will be a problem. But this is definitely something you're more of an expert on so I'll trust your judgement. Looking at other callers ofsynchronize_rcu()quite a few of them look to be in similar detach/release kind of situations though not sure how frequent and performance critical IOMMU domain detaching is in comparison.
Quoted 3 lines
Thanks,
Niklas
Addendum, of course independently of whether to use synchronize_rcu() I'll change the error handling in the IOTLB ops to not skip over the other devices.
Niklas Schnelle
maintainerPATCH 4/5 iommu/s390: Optimize IOMMU table walking
In reply to Niklas SchnelleWhen invalidating existing table entries for unmap there is no need to know the physical address beforehand so don't do an extra walk of the IOMMU table to get it. Also when invalidating entries not finding an entry indicates an invalid unmap and not a lack of memory we also don't need to undo updates in this case. Implement this by splitting s390_iommu_update_trans() in a variant for validating and one for invalidating translations.
--- drivers/iommu/s390-iommu.c | 69 ++++++++++++++++++++++++-------------- 1 file changed, 43 insertions(+), 26 deletions(-)
drivers/iommu/s390-iommu.c +43 -26
@@ -260,14 +260,14 @@ static void s390_iommu_iotlb_sync_map(struct iommu_domain *domain,rcu_read_unlock (); } -static int s390_iommu_update_trans (struct s390_domain *s390_domain, -phys_addr_t pa,dma_addr_t dma_addr, -unsigned long nr_pages,int flags) +static int s390_iommu_validate_trans (struct s390_domain *s390_domain, +phys_addr_t pa,dma_addr_t dma_addr, +unsigned long nr_pages,int flags) {phys_addr_t page_addr = pa &PAGE_MASK ;unsigned long irq_flags, i;unsigned long *entry; -int rc =0 ; +int rc;if (!nr_pages)return 0 ;
@@ -275,7 +275,7 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain,spin_lock_irqsave (&s390_domain->dma_table_lock, irq_flags);for (i =0 ; i < nr_pages; i++) { entry =dma_walk_cpu_trans (s390_domain->dma_table, dma_addr); -if (!entry) { +if (unlikely (!entry)) { rc = -ENOMEM ; goto undo_cpu_trans; }
@@ -283,19 +283,43 @@ static int s390_iommu_update_trans(struct s390_domain *s390_domain, page_addr +=PAGE_SIZE ; dma_addr +=PAGE_SIZE ; } +spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags); + +return 0 ; undo_cpu_trans: -if (rc && ((flags &ZPCI_PTE_VALID_MASK ) ==ZPCI_PTE_VALID )) { - flags =ZPCI_PTE_INVALID ; -while (i-- >0 ) { - page_addr -=PAGE_SIZE ; - dma_addr -=PAGE_SIZE ; - entry =dma_walk_cpu_trans (s390_domain->dma_table, - dma_addr); -if (!entry) -break ; -dma_update_cpu_trans (entry, page_addr, flags); +while (i-- >0 ) { + dma_addr -=PAGE_SIZE ; + entry =dma_walk_cpu_trans (s390_domain->dma_table, + dma_addr); +if (!entry) +break ; +dma_update_cpu_trans (entry,0 ,ZPCI_PTE_INVALID ); + } +spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags); + +return rc; +} + +static int s390_iommu_invalidate_trans (struct s390_domain *s390_domain, +dma_addr_t dma_addr,unsigned long nr_pages) +{ +unsigned long irq_flags, i; +unsigned long *entry; +int rc =0 ; + +if (!nr_pages) +return 0 ; + +spin_lock_irqsave (&s390_domain->dma_table_lock, irq_flags); +for (i =0 ; i < nr_pages; i++) { + entry =dma_walk_cpu_trans (s390_domain->dma_table, dma_addr); +if (unlikely (!entry)) { + rc = -EINVAL ; +break ; } +dma_update_cpu_trans (entry,0 ,ZPCI_PTE_INVALID ); + dma_addr +=PAGE_SIZE ; }spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags);
@@ -308,8 +332,8 @@ static int s390_iommu_map_pages(struct iommu_domain *domain, int prot, gfp_t gfp, size_t *mapped) { struct s390_domain *s390_domain = to_s390_domain(domain); -int flags =ZPCI_PTE_VALID , rc =0 ;size_t size = pgcount <<__ffs (pgsize); +int flags =ZPCI_PTE_VALID , rc =0 ;if (pgsize !=SZ_4K )return -EINVAL ;
@@ -327,8 +351,8 @@ static int s390_iommu_map_pages(struct iommu_domain *domain,if (!(prot &IOMMU_WRITE )) flags |=ZPCI_TABLE_PROTECTED ; - rc =s390_iommu_update_trans (s390_domain, paddr, iova, - pgcount, flags); + rc =s390_iommu_validate_trans (s390_domain, paddr, iova, + pgcount, flags);if (!rc) *mapped = size;
@@ -373,20 +397,13 @@ static size_t s390_iommu_unmap_pages(struct iommu_domain *domain, {struct s390_domain *s390_domain =to_s390_domain (domain);size_t size = pgcount <<__ffs (pgsize); -int flags =ZPCI_PTE_INVALID ; -phys_addr_t paddr;int rc;if (WARN_ON (iova < s390_domain->domain.geometry.aperture_start || (iova + size -1 ) > s390_domain->domain.geometry.aperture_end))return 0 ; - paddr =s390_iommu_iova_to_phys (domain, iova); -if (!paddr) -return 0 ; - - rc =s390_iommu_update_trans (s390_domain, paddr, iova, - pgcount, flags); + rc =s390_iommu_invalidate_trans (s390_domain, iova, pgcount);if (rc)return 0 ;
Signature · 1 line
2.34.1
Niklas Schnelle
maintainerPATCH 5/5 s390/pci: use lock-free I/O translation updates
In reply to Niklas SchnelleI/O translation tables on s390 use 8 byte page table entries and tables which are allocated lazily but only freed when the entire I/O translation table is torn down. Also each IOVA can at any time only translate to one physical address Furthermore I/O table accesses by the IOMMU hardware are cache coherent. With a bit of care we can thus use atomic updates to manipulate the translation table without having to use a global lock at all. This is done analogous to the existing I/O translation table handling code used on Intel and AMD x86 systems.
--- arch/s390/include/asm/pci.h | 1 - arch/s390/pci/pci_dma.c | 74 ++++++++++++++++++++++--------------- drivers/iommu/s390-iommu.c | 37 +++++++------------ 3 files changed, 58 insertions(+), 54 deletions(-)
arch/s390/include/asm/pci.h +0 -1
@@ -157,7 +157,6 @@ struct zpci_dev {/* DMA stuff */ unsigned long *dma_table; -spinlock_t dma_table_lock;int tlb_refresh;spinlock_t iommu_bitmap_lock;
arch/s390/pci/pci_dma.c +45 -29
134 lines not on this page · raw message
drivers/iommu/s390-iommu.c +13 -24
@@ -20,7 +20,6 @@ struct s390_domain {struct iommu_domain domain;struct list_head devices;unsigned long *dma_table; -spinlock_t dma_table_lock;spinlock_t list_lock; };
@@ -61,7 +60,6 @@ static struct iommu_domain *s390_domain_alloc(unsigned domain_type) s390_domain->domain.geometry.aperture_start =0 ; s390_domain->domain.geometry.aperture_end =ZPCI_TABLE_SIZE_RT -1 ; -spin_lock_init (&s390_domain->dma_table_lock);spin_lock_init (&s390_domain->list_lock);INIT_LIST_HEAD_RCU (&s390_domain->devices);
@@ -265,14 +263,10 @@ static int s390_iommu_validate_trans(struct s390_domain *s390_domain, unsigned long nr_pages, int flags) {phys_addr_t page_addr = pa &PAGE_MASK ; -unsigned long irq_flags, i;unsigned long *entry; +unsigned long i;int rc; -if (!nr_pages) -return 0 ; - -spin_lock_irqsave (&s390_domain->dma_table_lock, irq_flags);for (i =0 ; i < nr_pages; i++) { entry =dma_walk_cpu_trans (s390_domain->dma_table, dma_addr);if (unlikely (!entry)) {
@@ -283,7 +277,6 @@ static int s390_iommu_validate_trans(struct s390_domain *s390_domain, page_addr +=PAGE_SIZE ; dma_addr +=PAGE_SIZE ; } -spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags);return 0 ;
@@ -296,7 +289,6 @@ static int s390_iommu_validate_trans(struct s390_domain *s390_domain,break ;dma_update_cpu_trans (entry,0 ,ZPCI_PTE_INVALID ); } -spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags);return rc; }
@@ -304,14 +296,10 @@ static int s390_iommu_validate_trans(struct s390_domain *s390_domain,static int s390_iommu_invalidate_trans (struct s390_domain *s390_domain,dma_addr_t dma_addr,unsigned long nr_pages) { -unsigned long irq_flags, i;unsigned long *entry; +unsigned long i;int rc =0 ; -if (!nr_pages) -return 0 ; - -spin_lock_irqsave (&s390_domain->dma_table_lock, irq_flags);for (i =0 ; i < nr_pages; i++) { entry =dma_walk_cpu_trans (s390_domain->dma_table, dma_addr);if (unlikely (!entry)) {
@@ -321,7 +309,6 @@ static int s390_iommu_invalidate_trans(struct s390_domain *s390_domain,dma_update_cpu_trans (entry,0 ,ZPCI_PTE_INVALID ); dma_addr +=PAGE_SIZE ; } -spin_unlock_irqrestore (&s390_domain->dma_table_lock, irq_flags);return rc; }
@@ -363,7 +350,8 @@ static phys_addr_t s390_iommu_iova_to_phys(struct iommu_domain *domain, dma_addr_t iova) {struct s390_domain *s390_domain =to_s390_domain (domain); -unsigned long *sto, *pto, *rto, flags; +unsigned long *rto, *sto, *pto; +unsigned long ste, pte, rte;unsigned int rtx, sx, px;phys_addr_t phys =0 ;
@@ -376,16 +364,17 @@ static phys_addr_t s390_iommu_iova_to_phys(struct iommu_domain *domain, px =calc_px (iova); rto = s390_domain->dma_table; -spin_lock_irqsave (&s390_domain->dma_table_lock, flags); -if (rto &®_entry_isvalid (rto[rtx])) { - sto =get_rt_sto (rto[rtx]); -if (sto &®_entry_isvalid (sto[sx])) { - pto =get_st_pto (sto[sx]); -if (pto &&pt_entry_isvalid (pto[px])) - phys = pto[px] &ZPCI_PTE_ADDR_MASK ; + rte =READ_ONCE (rto[rtx]); +if (reg_entry_isvalid (rte)) { + sto =get_rt_sto (rte); + ste =READ_ONCE (sto[sx]); +if (reg_entry_isvalid (ste)) { + pto =get_st_pto (ste); + pte =READ_ONCE (pto[px]); +if (pt_entry_isvalid (pte)) + phys = pte &ZPCI_PTE_ADDR_MASK ; } } -spin_unlock_irqrestore (&s390_domain->dma_table_lock, flags);return phys; }
Signature · 1 line
2.34.1