Prev: Removing dead ARCH_GUMSTIX_ORIG
Next: What's the relationship between Linux driver running priority and FIFO policy?
From: Steven Rostedt on 21 Jul 2010 12:00
On Wed, 2010-07-21 at 11:22 -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jul 21, 2010 at 08:12:00AM +0530, Srikar Dronamraju escreveu:

> I guess this is what he means:
>
> [acme(a)doppio linux-2.6-tip]$ grep ' [TtWw] .\+\.' /proc/kallsyms | head -5
> ffffffff81000646 t trace_kmalloc.clone.0
> ffffffff810006ac t create_dev.clone.0
> ffffffff81006ae4 t test_ti_thread_flag.clone.0
> ffffffff8100a388 t trace_power_start.clone.0
> ffffffff8100ad8d t user_regset_copyin.clone.0
> [acme(a)doppio linux-2.6-tip]$ readelf -s ../build/v2.6.35-rc5-tip+/vmlinux | grep ' FUNC .\+\.' | head -5
> 165: ffffffff81000646 101 FUNC LOCAL DEFAULT 1 trace_kmalloc.clone.0
> 180: ffffffff810006ac 44 FUNC LOCAL DEFAULT 1 create_dev.clone.0
> 438: ffffffff81006ae4 22 FUNC LOCAL DEFAULT 1 test_ti_thread_flag.clone
> 510: ffffffff81ae5c40 136 FUNC LOCAL DEFAULT 22 e820_end_pfn.clone.0
> 750: ffffffff8100a388 65 FUNC LOCAL DEFAULT 1 trace_power_start.clone.0
> [acme(a)doppio linux-2.6-tip]$
>
> Or at least those are the ones with dots here.

Note, in PPC64 the function names all start with dots. That is, a
function name is just a symbol look up to the actual function which is
referenced by a '.'.


sys_read: points to .sys_read

.sys_read: actual address of start of function.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Removing dead ARCH_GUMSTIX_ORIG
Next: What's the relationship between Linux driver running priority and FIFO policy?