From: Xia Kaixu <kaixu.xia@linaro.org>
To: rmk+kernel@arm.linux.org.uk, arm@kernel.org
Cc: kaixu.xia@linaro.org, arnd@arndb.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] ARM: introduce a CONFIG_ARCH_MULTIPLATFORM_STRICT Kconfig option
Date: Tue, 28 Oct 2014 21:31:31 +0800 [thread overview]
Message-ID: <1414503095-25986-2-git-send-email-kaixu.xia@linaro.org> (raw)
In-Reply-To: <1414503095-25986-1-git-send-email-kaixu.xia@linaro.org>
The current allmodconfig kernel boot fails on OMAP4460. There
are several configuration options that can only work on a subset
of the available machines, and enabling them will break other
machines that may be enabled in a multiplatform kernel.
Now we introduce a CONFIG_ARCH_MULTIPLATFORM_STRICT Kconfig
option that prevent those other options from getting enabled
and get a strict multiplatform kernel.
Signed-off-by: Xia Kaixu <kaixu.xia@linaro.org>
---
arch/arm/Kconfig | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 89c4b5c..50762cc 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -840,6 +840,20 @@ config ARCH_MULTI_CPU_AUTO
endmenu
+config ARCH_MULTIPLATFORM_STRICT
+ bool "Only allow options that do not break other platforms"
+ depends on ARCH_MULTIPLATFORM
+ default y
+ help
+ There are several configuration options that can only work
+ on a subset of the available machines, and enabling them
+ will break running the kernel on other machines that may be
+ enabled in a multiplatform kernel.
+
+ Enabling ARCH_MULTIPLATFORM_STRICT will prevent those other
+ options from getting enabled, so the kernel should always
+ run on any hardware that is part of the configuration.
+
config ARCH_VIRT
bool "Dummy Virtual Machine" if ARCH_MULTI_V7
select ARM_AMBA
--
2.1.1
next prev parent reply other threads:[~2014-10-28 13:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:31 [PATCH v2 0/5] ARM: get a strict multiplatform kernel that can run on any hardware Xia Kaixu
2014-10-28 13:31 ` Xia Kaixu [this message]
2014-10-28 14:18 ` [PATCH v2 1/5] ARM: introduce a CONFIG_ARCH_MULTIPLATFORM_STRICT Kconfig option Arnd Bergmann
2014-10-28 14:21 ` Russell King - ARM Linux
2014-10-28 13:31 ` [PATCH v2 2/5] ARM: change the corresponding arm/mach defconfigs Xia Kaixu
2014-10-28 13:31 ` [PATCH v2 3/5] ARM: restrict CPU_BIG_ENDIAN configuration option Xia Kaixu
2014-10-28 14:00 ` Russell King - ARM Linux
2014-10-28 14:37 ` Arnd Bergmann
2014-10-28 14:53 ` Russell King - ARM Linux
2014-10-28 16:03 ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 4/5] ARM: allow errata and XIP options to be enabled without ARCH_MULTIPLATFORM_STRICT Xia Kaixu
2014-10-28 14:02 ` Russell King - ARM Linux
2014-10-28 14:24 ` Arnd Bergmann
2014-10-28 14:31 ` Russell King - ARM Linux
2014-10-28 14:50 ` Arnd Bergmann
2014-10-28 15:05 ` Russell King - ARM Linux
2014-10-28 15:32 ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 5/5] ARM: use early console instead of early debug in allmodconfig kernels Xia Kaixu
2014-10-28 14:05 ` Russell King - ARM Linux
2014-10-28 14:29 ` Arnd Bergmann
2014-10-28 14:35 ` Russell King - ARM Linux
2014-10-28 15:01 ` Arnd Bergmann
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=1414503095-25986-2-git-send-email-kaixu.xia@linaro.org \
--to=kaixu.xia@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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®