From: Libo Chen <libo.chen@oracle.com> To: masahiroy@kernel.org, tglx@linutronix.de, peterz@infradead.org, mingo@kernel.org Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org Subject: [PATCH] lib/Kconfig: remove DEBUG_PER_CPU_MAPS dependency for CPUMASK_OFFSTACK Date: Thu, 24 Mar 2022 16:18:59 -0700 [thread overview] Message-ID: <20220324231859.1287918-2-libo.chen@oracle.com> (raw) In-Reply-To: <20220324231859.1287918-1-libo.chen@oracle.com> Forcing CPUMASK_OFFSTACK to be conditoned on DEBUG_PER_CPU_MAPS doesn't make a lot of sense nowaday. Even the original patch dating back to 2008, aab46da0520a ("cpumask: Add CONFIG_CPUMASK_OFFSTACK") didn't give any rationale for such dependency. Nowhere in the code supports the presumption that DEBUG_PER_CPU_MAPS is necessary for CONFIG_CPUMASK_OFFSTACK. Make no mistake, it's good to have DEBUG_PER_CPU_MAPS for debugging purpose or precaution, but it's simply not a hard requirement for CPUMASK_OFFSTACK. Moreover, x86 Kconfig already can set CPUMASK_OFFSTACK=y without DEBUG_PER_CPU_MAPS=y. There is no reason other architectures cannot given the fact that they have even fewer, if any, arch-specific CONFIG_DEBUG_PER_CPU_MAPS code than x86. Signed-off-by: Libo Chen <libo.chen@oracle.com> --- lib/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig b/lib/Kconfig index 9b5a692ce00c..a017f5fe4e38 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -502,7 +502,7 @@ config CHECK_SIGNATURE bool config CPUMASK_OFFSTACK - bool "Force CPU masks off stack" if DEBUG_PER_CPU_MAPS + bool "Force CPU masks off stack" help Use dynamic allocation for cpumask_var_t, instead of putting them on the stack. This is a bit more expensive, but avoids -- 2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Libo Chen <libo.chen@oracle.com> To: masahiroy@kernel.org, tglx@linutronix.de, peterz@infradead.org, mingo@kernel.org Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org Subject: [PATCH] lib/Kconfig: remove DEBUG_PER_CPU_MAPS dependency for CPUMASK_OFFSTACK Date: Thu, 24 Mar 2022 16:18:59 -0700 [thread overview] Message-ID: <20220324231859.1287918-2-libo.chen@oracle.com> (raw) In-Reply-To: <20220324231859.1287918-1-libo.chen@oracle.com> Forcing CPUMASK_OFFSTACK to be conditoned on DEBUG_PER_CPU_MAPS doesn't make a lot of sense nowaday. Even the original patch dating back to 2008, aab46da0520a ("cpumask: Add CONFIG_CPUMASK_OFFSTACK") didn't give any rationale for such dependency. Nowhere in the code supports the presumption that DEBUG_PER_CPU_MAPS is necessary for CONFIG_CPUMASK_OFFSTACK. Make no mistake, it's good to have DEBUG_PER_CPU_MAPS for debugging purpose or precaution, but it's simply not a hard requirement for CPUMASK_OFFSTACK. Moreover, x86 Kconfig already can set CPUMASK_OFFSTACK=y without DEBUG_PER_CPU_MAPS=y. There is no reason other architectures cannot given the fact that they have even fewer, if any, arch-specific CONFIG_DEBUG_PER_CPU_MAPS code than x86. Signed-off-by: Libo Chen <libo.chen@oracle.com> --- lib/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig b/lib/Kconfig index 9b5a692ce00c..a017f5fe4e38 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -502,7 +502,7 @@ config CHECK_SIGNATURE bool config CPUMASK_OFFSTACK - bool "Force CPU masks off stack" if DEBUG_PER_CPU_MAPS + bool "Force CPU masks off stack" help Use dynamic allocation for cpumask_var_t, instead of putting them on the stack. This is a bit more expensive, but avoids -- 2.27.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-24 23:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 23:18 [PATCH 0/1] lib/Kconfig: remove DEBUG_PER_CPU_MAPS dependency for CPUMASK_OFFSTACK Libo Chen 2022-03-24 23:18 ` Libo Chen 2022-03-24 23:18 ` Libo Chen [this message] 2022-03-24 23:18 ` [PATCH] " Libo Chen
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=20220324231859.1287918-2-libo.chen@oracle.com \ --to=libo.chen@oracle.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=masahiroy@kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=tglx@linutronix.de \ /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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.