Hi Geert, > -----Original Message----- > From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > Sent: 20 January 2025 16:38 > Subject: [PATCH/LOCAL] arm64: renesas: defconfig: Disable CONFIG_PROVE_LOCKING > > Proving that all locking that occurs in the kernel runtime is mathematically correct has an impact on > performance. Hence it is disabled in most defconfigs. > > Suggested-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@xxxxxxxxxxx> > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > --- > Not intended for upstream merge. > To be applied to the topic/renesas-defconfig branch. > --- > arch/arm64/configs/renesas_defconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/arm64/configs/renesas_defconfig b/arch/arm64/configs/renesas_defconfig > index 30a865507d6e5ad4..a3a324ae9e3867ad 100644 > --- a/arch/arm64/configs/renesas_defconfig > +++ b/arch/arm64/configs/renesas_defconfig > @@ -455,5 +472,4 @@ CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_DEBUG_FS=y # > CONFIG_SCHED_DEBUG is not set -CONFIG_PROVE_LOCKING=y # CONFIG_FTRACE is not set This config used to catch lot of bugs during development. Now we need to apply It manually. But on the positive side, CIP uses renesas_defconfig for testing and that will have performance improvement with this change. So, Reviewed-by: Biju Das <biju.das.jz@xxxxxxxxxxxxxx> Cheers, Biju
