[PATCH][UTOPIC][CONFIG] Disable CONFIG_CONTEXT_TRACKING_FORCE (LP: #1349028)
Colin King
colin.king at canonical.com
Thu Jul 31 08:38:53 UTC 2014
From: Colin Ian King <colin.king at canonical.com>
The CONFIG_CONTEXT_TRACKING_FORCE should be disabled for
various reasons:
1. As described in the Kconfig "this option brings an
overhead that you don't want in production" and also
"Say Y only if you're working on the development of an
architecture backend for the context tracking."
Clearly for production kernel we should disable this.
2. Disabling this option also fixes bug LP:#1349028.
Note: I've not yet resolved why CONFIG_CONTEXT_TRACKING_FORCE
enabled causes the bug in the getitimer behaviour, for now disabling
this option is adequate; I'll look at that one I get back from
my vacation in a few weeks time.
Signed-off-by: Colin Ian King <colin.king at canonical.com>
---
debian.master/config/config.common.ubuntu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian.master/config/config.common.ubuntu b/debian.master/config/config.common.ubuntu
index 2c2524e..20117bc 100644
--- a/debian.master/config/config.common.ubuntu
+++ b/debian.master/config/config.common.ubuntu
@@ -1239,7 +1239,7 @@ CONFIG_CONSOLE_POLL=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_CONTEXT_TRACKING=y
-CONFIG_CONTEXT_TRACKING_FORCE=y
+# CONFIG_CONTEXT_TRACKING_FORCE is not set
CONFIG_COPS=m
CONFIG_COPS_DAYNA=y
CONFIG_COPS_TANGENT=y
--
1.7.9.5
More information about the kernel-team
mailing list