From: "tip-bot2 for Oleg Nesterov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>,
Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/urgent] sched/isolation: Make CONFIG_CPU_ISOLATION depend on CONFIG_SMP
Date: Thu, 03 Apr 2025 11:26:36 -0000 [thread overview]
Message-ID: <174367959697.14745.16991363734966983099.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250330134955.GA7910@redhat.com>
The following commit has been merged into the sched/urgent branch of tip:
Commit-ID: 975776841e689dd8ba36df9fa72ac3eca3c2957a
Gitweb: https://git.kernel.org/tip/975776841e689dd8ba36df9fa72ac3eca3c2957a
Author: Oleg Nesterov <oleg@redhat.com>
AuthorDate: Sun, 30 Mar 2025 15:49:55 +02:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Thu, 03 Apr 2025 13:08:04 +02:00
sched/isolation: Make CONFIG_CPU_ISOLATION depend on CONFIG_SMP
kernel/sched/isolation.c obviously makes no sense without CONFIG_SMP, but
the Kconfig entry we have right now:
config CPU_ISOLATION
bool "CPU isolation"
depends on SMP || COMPILE_TEST
allows the creation of pointless .config's which cause
build failures.
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20250330134955.GA7910@redhat.com
Closes: https://lore.kernel.org/oe-kbuild-all/202503260646.lrUqD3j5-lkp@intel.com/
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 681f38e..ab9b0c2 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -709,7 +709,7 @@ endmenu # "CPU/Task time and stats accounting"
config CPU_ISOLATION
bool "CPU isolation"
- depends on SMP || COMPILE_TEST
+ depends on SMP
default y
help
Make sure that CPUs running critical tasks are not disturbed by
prev parent reply other threads:[~2025-04-03 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 22:20 kernel/sched/isolation.c:50: undefined reference to `sched_numa_find_closest' kernel test robot
2025-03-26 9:35 ` Oleg Nesterov
2025-03-27 21:35 ` Ingo Molnar
2025-03-30 13:49 ` [PATCH] sched/isolation: forbid CONFIG_CPU_ISOLATION without CONFIG_SMP Oleg Nesterov
2025-03-30 19:23 ` [tip: sched/urgent] sched/isolation: Make CONFIG_CPU_ISOLATION depend on CONFIG_SMP tip-bot2 for Oleg Nesterov
2025-04-03 11:26 ` tip-bot2 for Oleg Nesterov [this message]
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=174367959697.14745.16991363734966983099.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.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
all inboxes | Powered by JetHome®