Skip to content

Commit 65ac955

Browse files
daxtensgregkh
authored andcommitted
powerpc: PPC_SECURE_BOOT should not require PowerNV
[ Upstream commit 5c5e46d ] In commit 61f879d ("powerpc/pseries: Detect secure and trusted boot state of the system.") we taught the kernel how to understand the secure-boot parameters used by a pseries guest. However, CONFIG_PPC_SECURE_BOOT still requires PowerNV. I didn't catch this because pseries_le_defconfig includes support for PowerNV and so everything still worked. Indeed, most configs will. Nonetheless, technically PPC_SECURE_BOOT doesn't require PowerNV any more. The secure variables support (PPC_SECVAR_SYSFS) doesn't do anything on pSeries yet, but I don't think it's worth adding a new condition - at some stage we'll want to add a backend for pSeries anyway. Fixes: 61f879d ("powerpc/pseries: Detect secure and trusted boot state of the system.") Signed-off-by: Daniel Axtens <dja@axtens.net> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20200924014922.172914-1-dja@axtens.net Signed-off-by: Sasha Levin <sashal@kernel.org>
1 parent 14f7c67 commit 65ac955

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

arch/powerpc/Kconfig

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -980,7 +980,7 @@ config PPC_MEM_KEYS
980980
config PPC_SECURE_BOOT
981981
prompt "Enable secure boot support"
982982
bool
983-
depends on PPC_POWERNV
983+
depends on PPC_POWERNV || PPC_PSERIES
984984
depends on IMA_ARCH_POLICY
985985
imply IMA_SECURE_AND_OR_TRUSTED_BOOT
986986
help

0 commit comments

Comments
 (0)