LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
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@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 08:27:39 +0200 [thread overview]
Message-ID: <946736c0-d3bc-ed87-70bc-93c0c3cb998a@molgen.mpg.de> (raw)
In-Reply-To: <YVxjgFScCZNwliMi@zn.tnic>
Dear Borislav,
Thank you for your reply.
Am 05.10.21 um 16:38 schrieb Borislav Petkov:
> On Tue, Oct 05, 2021 at 04:29:41PM +0200, Paul Menzel wrote:
>> Selecting the symbol `AMD_MEM_ENCRYPT` – as
>> done in Debian 5.13.9-1~exp1 [1] – also selects
>> `AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT`, as it defaults to yes,
>
> I'm assuming that "selecting" is done automatically: alldefconfig,
> olddefconfig?
>
> Because CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT only depends on
> CONFIG_AMD_MEM_ENCRYPT and former can be disabled in oldconfig or
> menuconfig etc.
Sorry for being unclear. Distributions want to enable support for that
feature, but as long as it breaks systems, it should be opt-in via the
Linux kernel command line, and not opt-out. Also the Kconfig help texts
do not mention anything about these problems, and the AMDGPU log message
is of level info and not error. It’d be even better, if the message
would contain the information, how to disable SME (`mem_encrypt=off`).
Kind regards,
Paul
next prev parent reply other threads:[~2021-10-06 6:27 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 [this message]
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
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=946736c0-d3bc-ed87-70bc-93c0c3cb998a@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bp@alien8.de \
--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=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: link
Be 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).