From: Randy Dunlap <randy.dunlap@oracle.com>
To: Simon W Bock <sbock@uni-tuebingen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KALLSYMS always enabled in 'make gconfig' on PS3 kernel
Date: Sun, 18 Jan 2009 15:59:43 -0800 [thread overview]
Message-ID: <4973C26F.70400@oracle.com> (raw)
In-Reply-To: <4972C77B.1070800@uni-tuebingen.de>
Simon W Bock wrote:
> Hi All,
> this seems to be the most appropriate place to report it...
Yes, or linux-kbuild@vger.kernel.org
> I try to compile a kernel on and for the PS3 using Geoff Levand's
> sources
> http://git.kernel.org/?p=linux/kernel/git/geoff/ps3-linux.git;a=summary
> and did a 'make ps3_defconfig' before doing 'make gconfig'.
> Now I'd care much more for 300k less in kernel size than for full
> symbols in the OOPS, so I would like to deselect KALLSYMS and
> KALLSYMS_ALL. The latter is even suggested to disable in the help text.
> But whatever I do, those two are always selected. Even when I deselect
> them using vi, the next time I do a 'make gconfig' on the config-file
> they are on again.
First, this isn't gconfig-specific. xconfig or menuconfig should
have the same behavior. At least I see it in xconfig also.
> Is this done for some special reason? Or can they be turned off?
All 3 of the KALLSYMS kconfig symbols are under the kconfig menu
prompt: "Configure standard kernel features (for small systems)",
which is not enabled in ps3_defconfig AFAICT (unless Geoff's is
modified from that I can see/test in linux-next). All that you
need to do is enable that config symbol (called CONFIG_EMBEDDED)
and then you can modify the KALLSYMS config symbols.
HTH.
--
~Randy
prev parent reply other threads:[~2009-01-19 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 6:08 KALLSYMS always enabled in 'make gconfig' on PS3 kernel Simon W Bock
2009-01-18 23:59 ` Randy Dunlap [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=4973C26F.70400@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbock@uni-tuebingen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.