Chris Metcalf <cmetcalf@xxxxxxxxxx> writes: > > +config TASK_ISOLATION_ALL > + bool "Provide task isolation on all CPUs by default (except CPU 0)" > + depends on TASK_ISOLATION > + help > + If the user doesn't pass the task_isolation boot option to > + define the range of task isolation CPUs, consider that all > + CPUs in the system are task isolation by default. > + Note the boot CPU will still be kept outside the range to > + handle timekeeping duty, etc. That seems like a very dangerous Kconfig option. "CONFIG_BREAK_EVERYTHING" If someone sets that by default they will have a lot of trouble. I wouldn't add that, make it a run time option only. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
