lkml.org 
[lkml]   [2006]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC PATCH 1/3] export symbol report: overview
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?

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-21 09:45    [W:0.047 / U:0.148 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site