From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Theodore Tso <tytso@mit.edu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/3] removing unwanted module configs
Date: Thu, 30 Apr 2009 16:42:20 +0200 [thread overview]
Message-ID: <20090430144220.GB14897@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0904300932380.20374@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> 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.
this is a basic usability issue. The main goal is to help regular
Linux users.
> I see I can use scripts/extract-ikconfig to get the config from
> the current image. Now which image should it try?
no, enable IKCONFIG_PROC and it will be under /proc/config.gz.
> /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.
yeah, that sounds like a good plan.
Ingo
prev parent reply other threads:[~2009-04-30 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 3:08 [PATCH 0/3] removing unwanted module configs Steven Rostedt
2009-04-30 3:08 ` [PATCH 1/3] kconfig: add streamline_config.pl to scripts Steven Rostedt
2009-04-30 3:08 ` [PATCH 2/3] kconfig: make localmodconfig to run streamline_config.pl Steven Rostedt
2009-04-30 3:08 ` [PATCH 3/3] kconfig: add make localyesconfig option Steven Rostedt
2009-04-30 7:18 ` [PATCH 0/3] removing unwanted module configs Ingo Molnar
2009-04-30 13:17 ` Steven Rostedt
2009-04-30 13:26 ` Ingo Molnar
2009-04-30 13:42 ` Steven Rostedt
2009-04-30 13:47 ` Steven Rostedt
2009-04-30 14:43 ` Ingo Molnar
2009-04-30 14:42 ` Ingo Molnar [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=20090430144220.GB14897@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=zippel@linux-m68k.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).