LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de> To: Tom Lendacky <thomas.lendacky@amd.com> Cc: Alex Deucher <alexdeucher@gmail.com>, Paul Menzel <pmenzel@molgen.mpg.de>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>, Dave Hansen <dave.hansen@linux.intel.com>, Andy Lutomirski <luto@kernel.org>, Peter Zijlstra <peterz@infradead.org>, LKML <linux-kernel@vger.kernel.org>, amd-gfx list <amd-gfx@lists.freedesktop.org> Subject: Re: `AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y` causes AMDGPU to fail on Ryzen: amdgpu: SME is not compatible with RAVEN Date: Wed, 6 Oct 2021 19:48:28 +0200 [thread overview] Message-ID: <YV3hbK/uhChK5Pse@zn.tnic> (raw) In-Reply-To: <96f6dbed-b027-c65e-6888-c0e8630cc006@amd.com> Ok, so I sat down and wrote something and tried to capture all the stuff we so talked about that it is clear in the future why we did it. Thoughts? --- From: Borislav Petkov <bp@suse.de> Date: Wed, 6 Oct 2021 19:34:55 +0200 Subject: [PATCH] x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically This Kconfig option was added initially so that memory encryption is enabled by default on machines which support it. However, Raven-class GPUs, a.o., cannot handle DMA masks which are shorter than the bit position of the encryption, aka C-bit. For that, those devices need to have the IOMMU present. If the IOMMU is disabled or in passthrough mode, though, the kernel would switch to SWIOTLB bounce-buffering for those transfers. In order to avoid that, 2cc13bb4f59f ("iommu: Disable passthrough mode when SME is active") disables the default IOMMU passthrough mode so that devices for which the default 256K DMA is insufficient, can use the IOMMU instead. However 2, there are cases where the IOMMU is disabled in the BIOS, etc, think the usual hardware folk "oops, I dropped the ball there" cases. Which means, it can happen that there are systems out there with devices which need the IOMMU to function properly with SME enabled but the IOMMU won't necessarily be enabled. So in order for those devices to function, drop the "default y" for the SME by default on option so that users who want to have SME, will need to either enable it in their config or use "mem_encrypt=on" on the kernel command line. Fixes: 7744ccdbc16f ("x86/mm: Add Secure Memory Encryption (SME) support") Reported-by: Paul Menzel <pmenzel@molgen.mpg.de> Signed-off-by: Borislav Petkov <bp@suse.de> Cc: <stable@vger.kernel.org> Link: https://lkml.kernel.org/r/8bbacd0e-4580-3194-19d2-a0ecad7df09c@molgen.mpg.de --- arch/x86/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 8055da49f1c0..6a336b1f3f28 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -1525,7 +1525,6 @@ config AMD_MEM_ENCRYPT config AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT bool "Activate AMD Secure Memory Encryption (SME) by default" - default y depends on AMD_MEM_ENCRYPT help Say yes to have system memory encrypted by default if running on -- 2.29.2 -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-10-06 17:48 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 14:29 `AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y` causes AMDGPU to fail on Ryzen: amdgpu: SME is not compatible with RAVEN Paul Menzel 2021-10-05 14:38 ` Borislav Petkov 2021-10-06 6:27 ` Paul Menzel 2021-10-05 14:48 ` Alex Deucher 2021-10-06 9:42 ` Borislav Petkov 2021-10-06 13:23 ` Alex Deucher 2021-10-06 13:46 ` Borislav Petkov 2021-10-06 14:01 ` Tom Lendacky 2021-10-06 17:48 ` Borislav Petkov [this message] 2021-10-06 18:10 ` Alex Deucher 2021-10-06 18:21 ` Alex Deucher 2021-10-06 19:32 ` Borislav Petkov 2021-10-07 6:14 ` Christian König 2021-10-06 18:21 ` Borislav Petkov 2021-10-06 18:36 ` Alex Deucher 2021-10-06 19:34 ` Borislav Petkov 2021-10-06 21:39 ` Tom Lendacky 2021-10-11 13:05 ` Paul Menzel 2021-10-11 13:11 ` Borislav Petkov 2021-10-11 13:27 ` Tom Lendacky 2021-10-11 13:52 ` Paul Menzel 2021-10-11 13:58 ` Tom Lendacky 2021-10-11 14:21 ` Paul Menzel 2021-10-11 14:28 ` Tom Lendacky 2021-10-11 14:32 ` Alex Deucher 2021-10-11 16:03 ` [PATCH -v2] x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically Borislav Petkov 2021-10-11 16:05 ` Alex Deucher 2021-10-11 16:29 ` Tom Lendacky 2021-10-11 17:18 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YV3hbK/uhChK5Pse@zn.tnic \ --to=bp@alien8.de \ --cc=alexdeucher@gmail.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=dave.hansen@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=luto@kernel.org \ --cc=mingo@redhat.com \ --cc=peterz@infradead.org \ --cc=pmenzel@molgen.mpg.de \ --cc=tglx@linutronix.de \ --cc=thomas.lendacky@amd.com \ --cc=x86@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).