Re: [PATCH v10 05/12] task_isolation: support CONFIG_TASK_ISOLATION_ALL

From	Andi Kleen <andi@firstfloor.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v10 05/12] task_isolation: support CONFIG_TASK_ISOLATION_ALL
Date	2016-03-03 19:40 +0100
Message-ID	<r8Gkh-2Ii-3@gated-at.bofh.it> (permalink)
References	<r8lIT-4R2-29@gated-at.bofh.it> <r8Gkh-2Ii-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Chris Metcalf <cmetcalf@ezchip.com> 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@linux.intel.com -- Speaking for myself only

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v10 05/12] task_isolation: support CONFIG_TASK_ISOLATION_ALL Andi Kleen <andi@firstfloor.org> - 2016-03-03 19:40 +0100
  Re: [PATCH v10 05/12] task_isolation: support  CONFIG_TASK_ISOLATION_ALL Andi Kleen <andi@firstfloor.org> - 2016-03-03 21:10 +0100

csiph-web