From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, rossb@google.com, sam@ravnborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Date: Sat, 16 Sep 2006 02:33:04 +0200 [thread overview]
Message-ID: <20060916003304.GC669@stusta.de> (raw)
In-Reply-To: <20060915164135.34adb303.akpm@osdl.org>
On Fri, Sep 15, 2006 at 04:41:35PM -0700, Andrew Morton wrote:
> On Fri, 15 Sep 2006 15:47:52 -0700
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> > On Fri, 15 Sep 2006 14:58:06 -0700 akpm@osdl.org wrote:
> >
> > >
> > > The patch titled
> > >
> > > allow /proc/config.gz to be built as a module
> > >
> > > has been added to the -mm tree. Its filename is
> > >
> > > allow-proc-configgz-to-be-built-as-a-module.patch
> > >
> > > See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> > > out what to do about this
> > >
> > > ------------------------------------------------------
> > > Subject: allow /proc/config.gz to be built as a module
> > > From: Ross Biro <rossb@google.com>
> >
> > When/where was this patch submitted? I seem to have missed it
> > (or it was so long ago that I forgot about it).
>
> Ross wrote it today and I stole it.
>
> > > The driver for /proc/config.gz consumes rather a lot of memory and it is in
> > > fact possible to build it as a module.
> >
> > Can you try to quantify "rather a lot of memory"?
>
> I confused it with /proc/kallsyms. No, /proc/config.gz doesn't use much
> memory.
>
> > > In some ways this is a bit risky, because the .config which is used for
> > > compiling kernel/configs.c isn't necessarily the same as the .config which was
> > > used to build vmlinux.
> >
> > and that's why a module wasn't allowed.
> > It's not worth the risk IMO.
>
> I'd want to be hearing from distro people on that - I'd expect that the
> .config which is used to build configs.ko would not differ from that which
> is used to build vmlinux.
>...
If you are concerned about memory usage, and you are anyway building a
kernel package for a distribution, the reasonable solution is
place the .config in /boot/config-...
That's also what I know from the Debian kernel packages.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-09-16 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>
2006-09-15 22:47 ` + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree Randy.Dunlap
2006-09-15 23:04 ` rossb
2006-09-15 23:11 ` Randy.Dunlap
2006-09-15 23:41 ` Andrew Morton
2006-09-16 0:14 ` Randy.Dunlap
2006-09-16 0:23 ` Olivier Galibert
2006-09-16 0:33 ` Adrian Bunk [this message]
2006-10-02 1:17 ` Randy Dunlap
2006-10-02 6:32 ` Olaf Hering
2006-09-16 11:47 ` Arjan van de Ven
2006-09-17 0:48 ` rossb
2006-09-17 1:13 ` Adrian Bunk
2006-10-02 7:08 Mikael Pettersson
2006-10-02 10:42 ` Olivier Galibert
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 11:23 Mikael Pettersson
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=20060916003304.GC669@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rossb@google.com \
--cc=sam@ravnborg.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