https://bugzilla.kernel.org/show_bug.cgi?id=211117 thomas.lendacky@xxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.lendacky@xxxxxxx --- Comment #17 from thomas.lendacky@xxxxxxx --- This sounds like a mismatch between the encryption bit in the kernel and the encryption bit in userspace. It looks like that should be taken care of by the dma_pgprot() call in dma_mmap_attrs() or in iommu_dma_mmap(). But maybe the force_dma_unencrypted() in arch/x86/mm/mem_encrypt.c needs to understand if the IOMMU is doing the mapping. Since, even if the device doesn't support 48-bit or higher DMA, it will still done encrypted because of the IOMMU. I don't see any dmesg output, is the IOMMU enabled? What happens if you do iommu=pt on the kernel command line? Alternatively, if you want memory encryption for your bare-metal system, you can see if the BIOS supports TSME (Transparent SME). Then you can remove mem_encrypt=on or add mem_encrypt=off (if enabled by default), and still get memory encryption. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
