This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug translator/7042] Make upstream kernel developers happy


------- Additional Comments From mhiramat at redhat dot com  2009-02-10 17:30 -------
> > > - Get rid of duplicate codes from runtime.
> > this needs more investigation. I assume that most of autoconfs will be removed
> 
> (But they can't, if we wish to still run on non-bleeding-edge kernels.)

Hmm, so, how about just branching sources for newer kernels?
Fortunately, we already have -R option.

> > and some of safety memory/register accessing code should be merged to upstream
> > kernel for debugging.
> 
> Sure, if there is upstream interest in those small and stable bits.

Those stuffs will be useful for other developers who want to write a
custom tracer in plain c.

> > > - Push useful parts of runtime code to upstream kernel(might be "kernel
> > > APIs for tracers").
> > 
> > As I said above, some of safety code should be merged, and other utility codes
> > including unwinder, map, statistics, taskfinder and so on.
> 
> The unwinder is blocked on more experience with it.
> The task-finder is blocked on utrace.
> 
> The map/statistics stuff could go, to see if kernel folks were interested in
> having it.  (Since this part has not needed porting effort, the status quo does
> not represent a cost to the project.)  Who wants to try proposing it?

It's a part of runtime merging task. We may need to provide some ftrace-based
examples for these parts as Frank did for utrace.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=7042

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]