On Mon, 14 Oct 2024 14:58:37 +0200, Ahmad Fatoum wrote:
> Devices can be inherently DMA coherent and thus dma_alloc_coherent could
> be implemented as a normal allocation.
>
> While using uncached memory in this case isn't wrong, it can lead
> to a a very stark performance degradation as identified in this patch[1]
> when barebox ran under KVM.
>
> [...]
Applied, thanks!
[1/6] dma: make DMA_ADDRESS_BROKEN type-safe
https://git.pengutronix.de/cgit/barebox/commit/?id=5f004115ac0f (link may not be stable)
[2/6] video: stm: use DMA_ADDRESS_BROKEN instead of NULL
https://git.pengutronix.de/cgit/barebox/commit/?id=2ca7fca692c0 (link may not be stable)
[3/6] crypto: caam - pbl-init: use DMA_ADDRESS_BROKEN instead of NULL
https://git.pengutronix.de/cgit/barebox/commit/?id=b3b20535573c (link may not be stable)
[4/6] net: designware: don't use dma_mapping_error for non-streaming DMA
https://git.pengutronix.de/cgit/barebox/commit/?id=0b2bc567a82a (link may not be stable)
[5/6] net: macb: fix DMA_ADDRESS_BROKEN in the coherent ring allocations
https://git.pengutronix.de/cgit/barebox/commit/?id=df13e1902a2c (link may not be stable)
[6/6] dma: give dma_alloc_coherent a device parameter
https://git.pengutronix.de/cgit/barebox/commit/?id=a4c9398795be (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
