+# this option can be used to select the type of process address\r
+# space randomization that is used in the system, for architectures\r
+# that support this feature.\r
+# 0 - turn the process address space randomization off. this is the\r
+# default for architectures that do not support this feature anyways,\r
+# and kernels that are booted with the "norandmaps" parameter.\r
+kernel.randomize_va_space=0\r
+\r
+# this parameter can be used to control the soft lockup detector.\r
+#\r
+# 0 - disable the soft lockup detector\r
+# 1 - enable the soft lockup detector\r
+#\r
+# the soft lockup detector monitors cpus for threads that are hogging the cpus\r
+# without rescheduling voluntarily, and thus prevent the 'watchdog/n' threads\r
+# from running. the mechanism depends on the cpus ability to respond to timer\r
+# interrupts which are needed for the 'watchdog/n' threads to be woken up by\r
+# the watchdog timer function, otherwise the nmi watchdog - if enabled - can\r
+# detect a hard lockup condition.\r
+#kernel.soft_watchdog=0\r
+\r
+# this value can be used to control on which cpus the watchdog may run.\r
+# the default cpumask is all possible cores, but if no_hz_full is\r
+# enabled in the kernel config, and cores are specified with the\r
+# nohz_full= boot argument, those cores are excluded by default.\r
+# offline cores can be included in this mask, and if the core is later\r
+# brought online, the watchdog will be started based on the mask value.\r
+#\r
+# typically this value would only be touched in the nohz_full case\r
+# to re-enable cores that by default were not running the watchdog,\r
+# if a kernel lockup was suspected on those cores.\r
+kernel.watchdog_cpumask=0,18\r