forked from Minki/linux
817fc978b5
virtio_max_dma_size() returns the maximum DMA mapping size of the virtio
device by querying dma_max_mapping_size() for the device when the DMA
API is in use for the vring. Unfortunately, the device passed is
initialised by register_virtio_device() and does not inherit the DMA
configuration from its parent, resulting in SWIOTLB errors when bouncing
is enabled and the default 256K mapping limit (IO_TLB_SEGSIZE) is not
respected:
| virtio-pci 0000:00:01.0: swiotlb buffer is full (sz: 294912 bytes), total 1024 (slots), used 725 (slots)
Follow the pattern used elsewhere in the virtio_ring code when calling
into the DMA layer and pass the parent device to dma_max_mapping_size()
instead.
Cc: Marc Zyngier <maz@kernel.org>
Cc: Quentin Perret <qperret@google.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Signed-off-by: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20211201112018.25276-1-will@kernel.org
Acked-by: Jason Wang <jasowang@redhat.com>
Tested-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Fixes:
|
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
virtio_balloon.c | ||
virtio_dma_buf.c | ||
virtio_input.c | ||
virtio_mem.c | ||
virtio_mmio.c | ||
virtio_pci_common.c | ||
virtio_pci_common.h | ||
virtio_pci_legacy_dev.c | ||
virtio_pci_legacy.c | ||
virtio_pci_modern_dev.c | ||
virtio_pci_modern.c | ||
virtio_ring.c | ||
virtio_vdpa.c | ||
virtio.c |