I can help with two of these.
>From the 2.0.39 kernel:
Kernel profiling support
CONFIG_PROFILE
This is for kernel hackers who want to know how much time the kernel
spends in the various procedures. The information is stored in
/proc/profile (enable the /proc filesystem!) and in order to read
it, you need the readprofile package from sunsite.unc.edu. Its
manpage gives information regarding the format of profiling data. To
become a kernel hacker, you can start with the Kernel Hacker's
Guide, available via FTP (user: anonymous) from
sunsite.unc.edu:/pub/Linux/docs/LDP. Mere mortals say N.
Profile shift count
CONFIG_PROFILE_SHIFT
This is used to adjust the granularity with which the addresses of
executed instructions get recorded in /proc/profile. But since you
enabled "Kernel profiling support", you must be a kernel hacker and
hence you know what this is about :-)
The 2.4.16 kernel still has profiling support, but the config options have
been replaced with a boot option (see init/main.c, look for "profile=").
Setting the "profile=" boot option turns on profiling, and the integer
value of the option sets the granularity.
So I suggest something like this:
Kernel profiling support (dead)
CONFIG_PROFILE
This option used to enable kernel profiling, but is now dead.
Use the boot option "profile=" instead.
Profile shift count (dead)
CONFIG_PROFILE_SHIFT
This option used to set the granularity of kernel profiling,
but is now dead. Use the boot option "profile=" instead.
My opinion is that as long as an option exists in the corpus, it is good
to have help text for it, even if the help text says "this option is dead"
or "this option is a merge artifact, don't bother setting it".
Michael C
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
