lkml.org 
[lkml]   [1996]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectProblem: how to identify source code points for latency profiling
On Sun, 9 Jun 1996, Alan Cox wrote:

> > what is the point of using __inline__ functions ...
> >
> > __inline__ void foo( arg ) {
>
> Arg is evaluated once. You don't get burned by nasty macro expansion
> side effects (especially since we nest inlines 3 deep in places).

i will use the IP pointer instead of __FILE__ and __LINE__ then, as a
global identifier for source code points. It's more robust anyways.

about transforming IP values (code addresses) into symbols later:

i guess line info is lost or hard to recover. I can do function name
matching, based on the symbol map [like readprofile], but this isnt enough
for identifying cli()-s and sti()-s in most cases :((

so this looks like trouble :( IP values are not human readable enough

-- mingo



\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.077 / U:1.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site