[Bug translator/7042] Make upstream kernel developers happy

["mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From mhiramat at redhat dot com  2009-01-22 17:12 -------
(In reply to comment #7)
>  - Systemtap itself
>   - Merging a part of runtime and basic tapset to kernel tree, which
>    will provide us a permanent API for systemtap generated code.
>   (BTW, I'd like to suggest modifying ftrace plug-able and systemtap
>    generating ftrace-plugin tracers. This will be more acceptable for
>    upstream because we don't need to add so many code).

What I suggested here is changing runtime code (and translator too).
It will lose some kind of backward compatibility, but since we can't bump ftrace
out from kernel any more, there is no way to merge runtime directly to kernel.
Instead of that, we have to use and improve ftrace interface for systemtap.

So, Here are what we have to do, I think
- Assign someone to runtime merging task, who may talk with kernel developers.
- Modify ftrace to support kernel modules. this might have to involve Steven
Rostedt.
- Modify staprun/stapio to support ftrace interface, and replace transport
functions with ftrace interfaces.
- Get rid of duplicate codes from runtime.
- Modify translator to generate ftrace module.
- Push useful parts of runtime code to upstream kernel(might be "kernel APIs for
tracers").

ftrace and systemtap should be able to coexist on the kenrel.


-- 


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.