[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCHv6] 01/28] build: import Kbuild/Kconfig from Linux 4.2

>>> On 01.12.15 at 21:04, <cardoe@xxxxxxxxxx> wrote:
> On 11/30/15 11:19 AM, Ian Campbell wrote:
>> On Mon, 2015-11-30 at 11:00 -0600, Doug Goldstein wrote:
>>> Since there is a request to have KEXEC and the UARTs
>>> configurable by the user
>> Who asked for this?
>> I have quite a strong preference for not adding _any_ new[*] user
>> configurable options in this first pass, since I think those need to be
>> considered quite carefully whereas this first series should be largely
>> about the mechanics of introducing Kconfig files.
>> Ian.
>> [*] i.e. anything which is not already controllable by the current .config
>> driven thing.
> The ARM UARTs are the take away I had from conversations with Julien
> Grall and reading past comments on the ML how people can change the ARM
> UARTs. Obviously if that's not desired I can drop that. I originally had
> them enabled as they are in config/arm{32,64}.mk and changed them to be
> user configurable later in the series.
> As far as KEXEC goes, its a user configurable option now in Rules.mk.
> You can build "make kexec=n" and it will disable it. I chose that one as
> an original example in v1 of how a user configurable option would look
> in this scheme.

And note how Ian said "_any_ new".

In fact as a follow-up we should convert other command line driven
overrides to config options (debug, perfc, bigmem, shadow) imo.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.