[PATCH v2 2/3] arm64: do not set SWIOTLB_NO_FORCE when swiotlb is required

[Juergen Gross]

On 12.05.21 22:18, Stefano Stabellini wrote:
> From: Christoph Hellwig <hch at lst.de>
> 
> Although SWIOTLB_NO_FORCE is meant to allow later calls to swiotlb_init,
> today dma_direct_map_page returns error if SWIOTLB_NO_FORCE.
> 
> For now, without a larger overhaul of SWIOTLB_NO_FORCE, the best we can
> do is to avoid setting SWIOTLB_NO_FORCE in mem_init when we know that it
> is going to be required later (e.g. Xen requires it).
> 
> CC: boris.ostrovsky at oracle.com
> CC: jgross at suse.com
> CC: catalin.marinas at arm.com
> CC: will at kernel.org
> CC: linux-arm-kernel at lists.infradead.org
> Fixes: 2726bf3ff252 ("swiotlb: Make SWIOTLB_NO_FORCE perform no allocation")
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> Signed-off-by: Stefano Stabellini <stefano.stabellini at xilinx.com>

Reviewed-by: Juergen Gross <jgross at suse.com>


Juergen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xB0DE9DD628BF132F.asc
Type: application/pgp-keys
Size: 3091 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20210514/ed2fc2fe/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20210514/ed2fc2fe/attachment-0001.sig>