* [PATCH 0/3 v2] Fix virtio-blk issue with SWIOTLB
@ 2019-01-15 13:22 Joerg Roedel
0 siblings, 0 replies; 2+ messages in thread
From: Joerg Roedel @ 2019-01-15 13:22 UTC (permalink / raw)
To: Michael S . Tsirkin, Jason Wang, Konrad Rzeszutek Wilk,
Christoph Hellwig
Cc: Jens Axboe, jroedel, brijesh.singh, joro, jon.grimm, jfehlig,
linux-kernel, linux-block, iommu, virtualization
Hi,
here is the second version of my patch-set to fix a DMA
mapping size issue triggered by the virtio-blk driver.
The problem is a limitation of the SWIOTLB implementation,
which does not support allocations larger than 256kb. When
the virtio-blk driver tries to read/write a block larger
than that, the allocation of the dma-handle fails and an IO
error is reported.
v1 of the patch-set can be found here:
https://lore.kernel.org/lkml/20190110134433.15672-1-joro@8bytes.org/
The change to v1 is that the maximum mapping size is now
officially propagated through the DMA-API, as suggested by
Christoph Hellwig.
Please review.
Thanks,
Joerg
Joerg Roedel (3):
swiotlb: Introduce swiotlb_max_mapping_size()
dma: Introduce dma_max_mapping_size()
virtio-blk: Consider dma_max_mapping_size() for maximum segment size
drivers/block/virtio_blk.c | 10 ++++++----
include/linux/dma-mapping.h | 16 ++++++++++++++++
include/linux/swiotlb.h | 5 +++++
kernel/dma/direct.c | 10 ++++++++++
kernel/dma/swiotlb.c | 5 +++++
5 files changed, 42 insertions(+), 4 deletions(-)
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* [PATCH 0/3 v2] Fix virtio-blk issue with SWIOTLB
@ 2019-01-15 13:22 Joerg Roedel
0 siblings, 0 replies; 2+ messages in thread
From: Joerg Roedel @ 2019-01-15 13:22 UTC (permalink / raw)
To: Michael S . Tsirkin, Jason Wang, Konrad Rzeszutek Wilk,
Christoph Hellwig
Cc: Jens Axboe, virtualization, linux-block, linux-kernel, iommu,
jfehlig, jon.grimm, brijesh.singh, joro, jroedel
Hi,
here is the second version of my patch-set to fix a DMA
mapping size issue triggered by the virtio-blk driver.
The problem is a limitation of the SWIOTLB implementation,
which does not support allocations larger than 256kb. When
the virtio-blk driver tries to read/write a block larger
than that, the allocation of the dma-handle fails and an IO
error is reported.
v1 of the patch-set can be found here:
https://lore.kernel.org/lkml/20190110134433.15672-1-joro@8bytes.org/
The change to v1 is that the maximum mapping size is now
officially propagated through the DMA-API, as suggested by
Christoph Hellwig.
Please review.
Thanks,
Joerg
Joerg Roedel (3):
swiotlb: Introduce swiotlb_max_mapping_size()
dma: Introduce dma_max_mapping_size()
virtio-blk: Consider dma_max_mapping_size() for maximum segment size
drivers/block/virtio_blk.c | 10 ++++++----
include/linux/dma-mapping.h | 16 ++++++++++++++++
include/linux/swiotlb.h | 5 +++++
kernel/dma/direct.c | 10 ++++++++++
kernel/dma/swiotlb.c | 5 +++++
5 files changed, 42 insertions(+), 4 deletions(-)
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-01-15 13:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-15 13:22 [PATCH 0/3 v2] Fix virtio-blk issue with SWIOTLB Joerg Roedel
2019-01-15 13:22 Joerg Roedel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.