lkml.org 
[lkml]   [2007]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
On Thu, May 10, 2007 at 05:14:25PM -0500, David Smith wrote:
> Christoph Hellwig wrote:
> >NACK. This shouldn't be includedable from userspace and systemtap people
> >should stop doing crap like that but use kernel infrastructure everyone
> >else uses including runtime kernel code instead of stuffin all kinds of
> >crap into their broken translator.
>
> Christoph,
>
> I was using the above information to parse all the available markers in
> a kernel, but I believe I've found a way where I don't need the marker.h
> header, so I'm OK with your NACK.
>
> Out of curiosity, what is the kernel infrastructure you believe I should
> be using to get a list of all available markers in a kernel? Note that
> I also have a requirement to get a list of all available markers in a
> kernel that isn't the currently running one.

None. Modules using markers should ship with the kernel or be written
on deman and not beeing created by some unreliable parser.
-
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: 2007-06-23 10:13    [W:0.119 / U:0.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site