On Wed, Oct 6, 2021 at 5:42 AM Borislav Petkov <bp@xxxxxxxxx> wrote: > > On Tue, Oct 05, 2021 at 10:48:15AM -0400, Alex Deucher wrote: > > It's not incompatible per se, but SEM requires the IOMMU be enabled > > because the C bit used for encryption is beyond the dma_mask of most > > devices. If the C bit is not set, the en/decryption for DMA doesn't > > occur. So you need IOMMU to be enabled in remapping mode to use SME > > with most devices. Raven has further requirements in that it requires > > IOMMUv2 functionality to support some features which currently uses a > > direct mapping in the IOMMU and hence the C bit is not properly > > handled. > > So lemme ask you this: do Raven-containing systems exist out there which > don't have IOMMUv2 functionality and which can cause boot failures when > SME is enabled in the kernel .config? There could be some OEM systems that disable the IOMMU on the platform and don't provide a switch in the bios to enable it. The GPU driver will still work in that case, it will just not be able to enable KFD support for ROCm compute. SME won't work for most devices in that case however since most devices have a DMA mask too small to handle the C bit for encryption. SME should be dependent on IOMMU being enabled. > > IOW, can we handle this at boot time properly, i.e., disable SME if we > detect Raven or IOMMUv2 support is missing? > > If not, then we really will have to change the default. I'm not an SME expert, but I thought that that was already the case. We just added the error condition in the GPU driver to prevent the driver from loading when the user forced SME on. IIRC, there were users that cared more about SME than graphics support. Alex > > Thx. > > -- > Regards/Gruss, > Boris. > > https://people.kernel.org/tglx/notes-about-netiquette
