On Thu, 1 Feb 2024 at 15:17, Tom Lendacky <thomas.lendacky@xxxxxxx> wrote: > > On 1/31/24 03:29, Borislav Petkov wrote: > > On Wed, Jan 31, 2024 at 10:12:13AM +0100, Ard Biesheuvel wrote: > >> The reason we need two flags is because there is no default value to > >> use when the command line param is absent. > > > > I think absent means memory encryption disabled like with every other > > option which is not present... > > > >> There is CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT but that one is AMD > > > > ... yes, and I'm thinking that it is time we kill this. I don't think > > anything uses it. It was meant well at the time. > > > > Let's wait for Tom to wake up first, though, as he might have some > > objections... > > I don't know if anyone is using the AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT > config option, but I don't have an issue removing it. > OK, I'll remove it in the next rev.
