swiotlb: Max mapping size takes min align mask into account
PATCH 1/1 swiotlb: Max mapping size takes min align mask into account
From: Tianyu Lan <[email protected]>
swiotlb_find_slots() skips slots according to io tlb aligned mask calculated from min aligned mask and original physical address offset. This affects max mapping size. The mapping size can't achieve the IO_TLB_SEGSIZE * IO_TLB_SIZE when original offset is non-zero. This will cause system boot up failure in Hyper-V Isolation VM where swiotlb force is enabled. Scsi layer use return value of dma_max_mapping_size() to set max segment size and it finally calls swiotlb_max_mapping_size(). Hyper-V storage driver sets min align mask to 4k - 1. Scsi layer may pass 256k length of request buffer with 0~4k offset and Hyper-V storage driver can't get swiotlb bounce buffer via DMA API. Swiotlb_find_slots() can't find 256k length bounce buffer with offset. Make swiotlb_max_mapping _size() take min align mask into account.
--- kernel/dma/swiotlb.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
kernel/dma/swiotlb.c +12 -1
@@ -743,7 +743,18 @@ dma_addr_t swiotlb_map(struct device *dev, phys_addr_t paddr, size_t size,size_t swiotlb_max_mapping_size (struct device *dev) { -return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE ; +int min_align_mask =dma_get_min_align_mask (dev); +int min_align =0 ; + +/* +* swiotlb_find_slots() skips slots according to +* min align mask. This affects max mapping size. +* Take it into acount here. +*/ +if (min_align_mask) + min_align =roundup (min_align_mask,IO_TLB_SIZE ); + +return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE - min_align; }bool is_swiotlb_active (struct device *dev)
Signature · 6 lines
2.25.1 _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
Robin Murphy
reviewerQuoted 15 lines · Tianyu Lan
From: Tianyu Lan <[email protected]>
swiotlb_find_slots()skips slots according to io tlb aligned mask calculated from min aligned mask and original physical address offset. This affects max mapping size. The mapping size can't achieve theIO_TLB_SEGSIZE*IO_TLB_SIZEwhen original offset is non-zero. This will cause system boot up failure in Hyper-V Isolation VM where swiotlb force is enabled. Scsi layer use return value ofdma_max_mapping_size()to set max segment size and it finally callsswiotlb_max_mapping_size(). Hyper-V storage driver sets min align mask to 4k - 1. Scsi layer may pass 256k length of request buffer with 0~4k offset and Hyper-V storage driver can't get swiotlb bounce buffer via DMA API.Swiotlb_find_slots()can't find 256k length bounce buffer with offset. Makeswiotlb_max_mapping_size()take min align mask into account.
Hmm, this seems a bit pessimistic - the offset can vary per mapping, so it feels to me like it should really be the caller's responsibility to account for it if they're already involved enough to care about both constraints. But I'm not sure how practical that would be.
Robin.
Quoted 19 lines
Signed-off-by Tianyu Lan <[email protected]>--- kernel/dma/swiotlb.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)kernel/dma/swiotlb.c +5
-1@@ -743,7 +743,18 @@ dma_addr_t swiotlb_map(struct device *dev, phys_addr_t paddr, size_t size,size_t swiotlb_max_mapping_size (struct device *dev) { -return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE ; +int min_align_mask =dma_get_min_align_mask (dev); +int min_align =0 ; + +/* +* swiotlb_find_slots() skips slots according to
kernel/dma/swiotlb.c dma_addr_t swiotlb_map(struct device *dev, phys_addr_t paddr, size_t size, · line 760
Quoted 10 lines
kernel/dma/swiotlb.c +7
-0+* min align mask. This affects max mapping size. +* Take it into acount here. +*/ +if (min_align_mask) + min_align =roundup (min_align_mask,IO_TLB_SIZE ); + +return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE - min_align; }bool is_swiotlb_active (struct device *dev)
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
From: Robin Murphy <[email protected]> Sent: Tuesday, May 10, 2022 9:34 AM
Quoted 18 lines · Tianyu Lan
Quoted 15 lines
From: Tianyu Lan <[email protected]>
swiotlb_find_slots()skips slots according to io tlb aligned mask calculated from min aligned mask and original physical address offset. This affects max mapping size. The mapping size can't achieve theIO_TLB_SEGSIZE*IO_TLB_SIZEwhen original offset is non-zero. This will cause system boot up failure in Hyper-V Isolation VM where swiotlb force is enabled. Scsi layer use return value ofdma_max_mapping_size()to set max segment size and it finally callsswiotlb_max_mapping_size(). Hyper-V storage driver sets min align mask to 4k - 1. Scsi layer may pass 256k length of request buffer with 0~4k offset and Hyper-V storage driver can't get swiotlb bounce buffer via DMA API.Swiotlb_find_slots()can't find 256k length bounce buffer with offset. Makeswiotlb_max_mapping_size()take min align mask into account.
Quoted 4 lines
Hmm, this seems a bit pessimistic - the offset can vary per mapping, so it feels to me like it should really be the caller's responsibility to account for it if they're already involved enough to care about both constraints. But I'm not sure how practical that would be.
Tianyu and I discussed this prior to his submitting the patch. Presumably dma_max_mapping_size() exists so that the higher level blk-mq code can limit the size of I/O requests to something that will "fit" in the swiotlb when bounce buffering is enabled. Unfortunately, the current code is just giving the wrong answer when the offset is non-zero. The offset would be less than PAGE_SIZE, so the impact would be dma_max_mapping_size() returning 252 Kbytes instead of 256 Kbytes, but only for devices where dma min align mask is set. And any I/O sizes less than 252 Kbytes are unaffected even when dma min align mask is set. Net, the impact would be only in a fairly rare edge case.
Even on ARM64 with a 64K page size, the Hyper-V storage driver is setting the dma min align mask to only 4K (which is correct because the Hyper-V host uses a 4K page size even if the guest is using something larger), so again the limit becomes 252 Kbytes instead of 256 Kbytes, and any impact is rare.
As you mentioned, how else would a caller handle this situation?
Michael
Quoted 32 lines
Robin.
kernel/dma/swiotlb.c dma_addr_t swiotlb_map(struct device *dev, phys_addr_t
Quoted 10 lines
Signed-off-by Tianyu Lan <[email protected]>--- kernel/dma/swiotlb.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)kernel/dma/swiotlb.c +0
-0@@ -743,7 +743,18 @@ dma_addr_t swiotlb_map(struct device *dev, phys_addr_tpaddr,
size_tsize,Quoted 18 lines
kernel/dma/swiotlb.c +12
-1size_t swiotlb_max_mapping_size (struct device *dev) { -return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE ; +int min_align_mask =dma_get_min_align_mask (dev); +int min_align =0 ; + +/* +* swiotlb_find_slots() skips slots according to +* min align mask. This affects max mapping size. +* Take it into acount here. +*/ +if (min_align_mask) + min_align =roundup (min_align_mask,IO_TLB_SIZE ); + +return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE - min_align; }
Quoted 1 line
kernel/dma/swiotlb.c dma_addr_t swiotlb_map(struct device *dev, phys_addr_t paddr, size_t size, · line 760
Quoted 1 line
kernel/dma/swiotlb.c +0
-0bool is_swiotlb_active (struct device *dev)
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Quoted 9 lines · Michael Kelley (LINUX)
Quoted 4 lines
Hmm, this seems a bit pessimistic - the offset can vary per mapping, so it feels to me like it should really be the caller's responsibility to account for it if they're already involved enough to care about both constraints. But I'm not sure how practical that would be.
Tianyu and I discussed this prior to his submitting the patch. Presumably
dma_max_mapping_size()exists so that the higher level blk-mq code can limit the size of I/O requests to something that will "fit" in the swiotlb when bounce buffering is enabled.
Yes, the idea that upper level code doesn't need to care was very much the idea behind dma_max_mapping_size().
Quoted 1 line
As you mentioned, how else would a caller handle this situation?
Well, we could look at dma_get_min_align_mask in the caller and do the calculation there, but I really don't think that is a good idea.
So this patch looks sensible to me.
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
Thanks,
applied to the dma-mapping for-next tree.
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu