>>> Julien Grall <julien.gr...@arm.com> 06/27/17 9:20 AM >>> >On 06/27/2017 07:04 AM, Jan Beulich wrote: >>>>> Andrew Cooper <andrew.coop...@citrix.com> 06/26/17 6:40 PM >>> >>>> --- a/xen/common/Kconfig >>>> +++ b/xen/common/Kconfig >>>> @@ -226,7 +226,7 @@ config CRYPTO >>>> bool >>>> >>>> config LIVEPATCH >>>> - bool "Live patching support (TECH PREVIEW)" >>>> + bool "Live patching support" >>>> default n >>> >>> This default should flip as well. >> >> For unstable maybe. But please not for 4.9 - people shouldn't be caught by >> surprise after 9 RCs that a config option's default changes. Furthermore, if >> we default it to y, will there be much of a difference to simply removing the >> config option? > >I think we should allow user to disable livepatch at build time. I have >mind any people looking at using Xen in constraint environment and >require some certifications. They will likely want to disable some part >of the Xen.
The at least I'd like to see it gain an EXPERT dependency. For now our overall goal still is to limit the number of possible different configurations. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
