On Fri, Jul 12, 2019 at 04:51:53PM +0200, Halil Pasic wrote: > Thank you very much! I will have another look, but it seems to me, > without further measures taken, this would break protected virtualization > support on s390. The effect of the che for s390 is that > force_dma_unencrypted() will always return false instead calling into > the platform code like it did before the patch, right? > > Should I send a Fixes: e67a5ed1f86f "dma-direct: Force unencrypted DMA > under SME for certain DMA masks" (Tom Lendacky, 2019-07-10) patch that > rectifies things for s390 or how do we want handle this? Yes, please do. I hadn't noticed the s390 support had landed in mainline already.
