From: Adrian Bunk <bunk@stusta.de>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org, arjan@infradead.org,
greg@kroah.com, hch@infradead.org, mathur@us.ibm.com
Subject: Re: [RFC PATCH 1/3] export symbol report: overview
Date: Fri, 21 Apr 2006 11:39:14 +0200 [thread overview]
Message-ID: <20060421093914.GD19754@stusta.de> (raw)
In-Reply-To: <1145607615.7323.212.camel@localhost>
On Fri, Apr 21, 2006 at 01:20:15AM -0700, Ram Pai wrote:
> On Fri, 2006-04-21 at 09:43 +0200, Sam Ravnborg wrote:
> > On Thu, Apr 20, 2006 at 03:36:53PM -0700, Ram Pai wrote:
> > > This patch series enables on-demand report generation of export symbol usage by
> > > inkernel modules. The report is available at
> > >
> > > A report generated by executing
> > > make allmodconfig
> > > make export_report
> > > is available at http://www.sudhaa.com/~ram/misc/export_report.txt
> > >
> > > This report lists:
> > > 1. the usage count of all exported symbols by in-kernel modules.
> > > 2. For each in-kernel module lists
> > > a) the in-kernel modules it depend on.
> > > b) list of exported symbols from that in-kernel modules it depend on.
> > >
> > > Highlights:
> > > On x86 architecture
> > > (1) 880 exported symbols not used by any in-kernel modules.
> > > (2) 1792 exported symbols used only once.
> > >
> > > This patch series has comments by Adrian Bunk incorporated.
> >
> > Hi Ram Pai.
> >
> > In principle what your patch does is a simple port-processign of
> > Module.symvers.
> > Insead of introducing another step in the buildprocess then for this
> > functionality we should just call your script direct.
> > This is not something the average users will do often, so having to
> > type:
> > ./scripts/export-report.pl
> >
> > And then let the perl script pick up default values for where to find
> > *.mod.c files and Module.symvers.
> >
> > Thoughts?
>
> Well, if the Module.symvers file does not exist than the script will
> fail; unless the script invokes the 'make modules'.
>
> Incorporating it into the Makefile can ease its use,
> because we can transparently trigger rules that can make the
> Module.symvers file.
>
> I guess its a question of which way makes it easy to use? and my
> thoughts are leaning towards incorporating it into the Makefile.
>
> I can make it either way. You suggest.
Sam is the one who can judge best on how to implement your proposal
best, but there's one thing you should have in mind:
This is a script that isn't for users compiling their own kernel - it's
a tool only a small subset of the kernel developers will use.
It does therefore not need a sophisticated error handling for cases like
a not yet compiled kernel or CONFIG_MODULES=n.
> RP
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-04-21 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 22:36 [RFC PATCH 1/3] export symbol report: overview Ram Pai
2006-04-21 7:43 ` Sam Ravnborg
2006-04-21 8:20 ` Ram Pai
2006-04-21 9:39 ` Adrian Bunk [this message]
2006-04-21 9:34 ` Adrian Bunk
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=20060421093914.GD19754@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mathur@us.ibm.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