search for: 9491ae4

...devices. >>> >>> There is a problem with the platform block device on that same model. >>> Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which >>> limits the number of mappings. >>> >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >>> based on read-ahead setting") unlocked read-ahead, we quickly run into >>> the limit of swiotlb and panic: >>> >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >>> (sz: 491520 byt...

...devices. >>> >>> There is a problem with the platform block device on that same model. >>> Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which >>> limits the number of mappings. >>> >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >>> based on read-ahead setting") unlocked read-ahead, we quickly run into >>> the limit of swiotlb and panic: >>> >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >>> (sz: 491520 byt...

...we can safely use the DMA API for all virtio devices. > > There is a problem with the platform block device on that same model. > Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which > limits the number of mappings. > > It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > based on read-ahead setting") unlocked read-ahead, we quickly run into > the limit of swiotlb and panic: > > [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > (sz: 491520 bytes) > [ 5.382452] virtio-mmio 1c1...

...we can safely use the DMA API for all virtio devices. > > There is a problem with the platform block device on that same model. > Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which > limits the number of mappings. > > It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > based on read-ahead setting") unlocked read-ahead, we quickly run into > the limit of swiotlb and panic: > > [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > (sz: 491520 bytes) > [ 5.382452] virtio-mmio 1c1...

Booting Linux on an ARM fastmodel containing an SMMU emulation results in an unexpected I/O page fault from the legacy virtio-blk PCI device: [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010 [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000 [ 1.211959] arm-smmu-v3 2b400000.smmu: 0x00000008fa081002 [

Booting Linux on an ARM fastmodel containing an SMMU emulation results in an unexpected I/O page fault from the legacy virtio-blk PCI device: [ 1.211721] arm-smmu-v3 2b400000.smmu: event 0x10 received: [ 1.211800] arm-smmu-v3 2b400000.smmu: 0x00000000fffff010 [ 1.211880] arm-smmu-v3 2b400000.smmu: 0x0000020800000000 [ 1.211959] arm-smmu-v3 2b400000.smmu: 0x00000008fa081002 [

...at 11:24:04AM +0000, Robin Murphy wrote: > On 06/01/17 21:51, Andy Lutomirski wrote: > > On Fri, Jan 6, 2017 at 10:32 AM, Robin Murphy <robin.murphy at arm.com> wrote: > >> On 06/01/17 17:48, Jean-Philippe Brucker wrote: > >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > >>> based on read-ahead setting") unlocked read-ahead, we quickly run into > >>> the limit of swiotlb and panic: > >>> > >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > &gt...

...DMA API for all virtio devices. >> >> There is a problem with the platform block device on that same model. >> Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which >> limits the number of mappings. >> >> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size >> based on read-ahead setting") unlocked read-ahead, we quickly run into >> the limit of swiotlb and panic: >> >> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full >> (sz: 491520 bytes) >> [ 5....

...evice-tree or > IORT), then we can safely use the DMA API for all virtio devices. There is a problem with the platform block device on that same model. Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which limits the number of mappings. It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size based on read-ahead setting") unlocked read-ahead, we quickly run into the limit of swiotlb and panic: [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full (sz: 491520 bytes) [ 5.382452] virtio-mmio 1c130000.virtio_block: DMA: Out o...

...; >>> There is a problem with the platform block device on that same model. > >>> Since it's not behind the SMMU, the DMA ops fall back to swiotlb, which > >>> limits the number of mappings. > >>> > >>> It used to work with 4.9, but since 9491ae4 ("mm: don't cap request size > >>> based on read-ahead setting") unlocked read-ahead, we quickly run into > >>> the limit of swiotlb and panic: > >>> > >>> [ 5.382359] virtio-mmio 1c130000.virtio_block: swiotlb buffer is full > &gt...