From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Bird, Tim" <Tim.Bird@sonymobile.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [Ksummit-discuss] RFC: Kernel tinification - kernel config reduction
Date: Fri, 15 Aug 2014 04:04:56 -0700 [thread overview]
Message-ID: <53EDE958.1040200@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdVQkqiE_S3ZAFziYXT4qESeofvC-6MsXfo_pYJxez2udQ@mail.gmail.com>
On 08/14/2014 02:02 AM, Geert Uytterhoeven wrote:
> Hi Günther,
>
> CC kbuild
>
> On Thu, Aug 14, 2014 at 10:50 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>> On 08/14/2014 12:40 AM, Geert Uytterhoeven wrote:
>>>> Maybe something like
>>>>
>>>> make PCI=n allmodconfig
>>>> make GPIOLIB=n allmodconfig
>>>>
>>>> which would let me disable key options selectively so I can improve
>>>> compile
>>>> coverage without having to go through all configurations (or randconfig).
>>>
>>>
>>> That's doable, using KCONFIG_ALLCONFIG.
>>>
>> I'll play with it some more, but a quick glance (and test) suggests that I
>> can
>> only use it to force a configuration option to be true, not to force it to
>> be false. Also, there seems to be an odd side effect.
>>
>> With
>> kconfig.gpio: "CONFIG_GPIOLIB=y"
>> and
>> kconfig.nogpio: "# CONFIG_GPIOLIB is not set"
>>
>> KCONFIG_ALLCONFIG=kconfig.gpio make allnoconfig
>> causes CONFIG_GPIOLIB to be set.
>>
>> KCONFIG_ALLCONFIG=kconfig.gpio make allmodconfig
>> KCONFIG_ALLCONFIG=kconfig.nogpio make allmodconfig
>> both have the odd and at least for me unexpected effect of disabling
>> CONFIG_MODULES, but do not affect CONFIG_GPIOLIB.
>
> Strange...
>
> I also saw strange things with randconfig, needing config input during the
> subsequent build, or "make oldconfig" asking new questions, just after
> having done a randconfig.
>
I made some progress. The following KCONFIG_ALLCONFIG file lets me disable GPIOLIB
with x86_64, and still build everything as modules.
# CONFIG_FB_VIA is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_GPIOLIB is not set
CONFIG_MODULES=y
I had to deselect everything which explicitly selects GPIOLIB. Kind of makes sense.
For some reason it is necessary to specify "CONFIG_MODULES=y" even with "allmodconfig"
when using a KCONFIG_ALLCONFIG file.
Guenter
prev parent reply other threads:[~2014-08-15 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F5184659D418E34EA12B1903EE5EF5FD0130D4AC5B90@seldmbx02.corpusers.net>
[not found] ` <20140813180743.GB16662@roeck-us.net>
[not found] ` <CAMuHMdVEYEsk1EtBbAAinJ=7m5SRh-w4DZb=_N0gaMgpvtRadw@mail.gmail.com>
[not found] ` <20140813224507.GA29606@roeck-us.net>
[not found] ` <CAMuHMdXZWhLtTzUnPymSt-P=viz7O7fq8nFaM-mHLT+XMnRJcA@mail.gmail.com>
[not found] ` <53EC7839.3010704@roeck-us.net>
2014-08-14 9:02 ` [Ksummit-discuss] RFC: Kernel tinification - kernel config reduction Geert Uytterhoeven
2014-08-15 11:04 ` Guenter Roeck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EDE958.1040200@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Tim.Bird@sonymobile.com \
--cc=geert@linux-m68k.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).