From: Takashi Iwai <tiwai@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: diet-kconfig: a script to trim unneeded kconfigs
Date: Fri, 19 Sep 2008 00:14:23 +0200 [thread overview]
Message-ID: <s5hr67hje4g.wl%tiwai@suse.de> (raw)
In-Reply-To: <31195.1221772167@turing-police.cc.vt.edu>
At Thu, 18 Sep 2008 17:09:27 -0400,
Valdis.Kletnieks@vt.edu wrote:
>
> On Thu, 18 Sep 2008 22:17:22 +0200, Takashi Iwai said:
>
> > There are different perspectives for this. My goal to reduce the
> > build time with the existing kernel config for a specific hardware.
> > That is, it makes eaiser to create another set of kernel with test
> > patches or bisect.
>
> One has to be careful here - I've more than once hit kernel bugs that I ended
> up bisecting, which were dependent on the exact .config used.
That's true. But, you should at least test the trimmed kernel once
before bisecting to reproduce the bug.
And, my script doesn't do anything so intrusive. It trims just unused
CONFIG_*=m. Since they are not loaded anyway, reducing them must be
harmless (in theory).
> The most recent
> was a deadlock during early boot if CONFIG_HID_COMPAT=y, which would have
> been turned off by any sane kconfig trimmer. On the flip side, running a
> trimmer wouldn't minimize my .config very much, because I've already set most
> stuff I *never* use to 'n'.
Heh, you are obviously not a "typical" user ;)
My scenario was for users of distro kernel who want to help debugging
with some given patches or bisecting.
> And more than once, I've had a bisect go horribly awry and need to be re-started
> because the bisect crossed back and forth over a commit that added a config
> option, so doing a 'make oldconfig' at each iteration would re-prompt, and
> I wasn't consistent in the reply I gave. Usually doesn't matter, except when
> the broken code is in the support for the feature...
Bisect isn't perfect, indeed. But, in many cases, it can catch
the harmful commit more easily, especially if it's in the area
where you are unfamiliar.
> I *do* keep around a *very* minimal "only what I need to get to single-user"
> config if build time is an issue...
>
> Might be different if you're starting off with a distro config that's basically
> an 'allmodconfig' - lotta fat to trim off *that*....
Exactly.
thanks,
Takashi
prev parent reply other threads:[~2008-09-18 22:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 23:55 Takashi Iwai
2008-09-18 14:01 ` Giacomo A. Catenazzi
2008-09-18 20:09 ` Takashi Iwai
2008-09-18 15:25 ` Mauro Carvalho Chehab
2008-09-18 15:43 ` Giacomo A. Catenazzi
2008-09-18 16:27 ` Mauro Carvalho Chehab
2008-09-19 9:12 ` Giacomo A. Catenazzi
2008-09-19 16:01 ` Takashi Iwai
2008-09-19 23:55 ` Chris Li
2008-09-19 23:57 ` Chris Li
2008-09-22 10:01 ` Takashi Iwai
2008-09-22 13:39 ` Giacomo A. Catenazzi
2008-09-22 15:41 ` Steven Rostedt
2008-09-22 15:50 ` Takashi Iwai
2008-09-22 19:25 ` Chris Li
2008-09-23 11:31 ` Takashi Iwai
2008-09-23 18:15 ` Chris Li
2008-09-23 18:50 ` Takashi Iwai
2008-09-23 19:40 ` Chris Li
2008-09-18 20:20 ` Takashi Iwai
2008-09-18 20:17 ` Takashi Iwai
2008-09-18 21:09 ` Valdis.Kletnieks
2008-09-18 22:14 ` Takashi Iwai [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=s5hr67hje4g.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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
all inboxes | Powered by JetHome®