[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0904300932380.20374@gandalf.stny.rr.com>
Date: Thu, 30 Apr 2009 09:42:12 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...e.hu>
cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Theodore Tso <tytso@....edu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
zippel@...ux-m68k.org, linux-kbuild@...r.kernel.org,
Sam Ravnborg <sam@...nborg.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH 0/3] removing unwanted module configs
On Thu, 30 Apr 2009, Ingo Molnar wrote:
>
> CONFIG_IKCONFIG=y would be a one-off thing, only to make the whole
> concept self-hosting. If i boot a localyesconfig kernel, how does
> the script figure out what is built in? It cannot, unless i provide
> it the precise .config - but often that wont be provided. The script
> should clone the environment it is running in really.
Does IKCONFIG get loaded in the running kernel if IKCONFIG_PROC is not
set, or does it just sit in the vmlinux file.
Since this option can also be used for helping embedded developers (I used
it for that) I would not want to bloat the kernel with running a script
that is suppose to minimize it. But if IKCONFIG && !IKCONFIG_PROC does not
add more data to the kernel, then I would be happy to turn it on by
default.
I see I can use scripts/extract-ikconfig to get the config from the
current image. Now which image should it try?
/boot/vmlinuz-`uname -r`
./vmlinux
I could have it first try /proc/config.gz and if it does not find it then
try the /boot kernel, if it does not find it or does not find a config
file in it, it would then try ./vmlinux file. If it does not find the file
or the config then it would just use the local .config.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists