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 kprobes/4384] Problem in making kprobe modules portable across all the archtecture.


------- Additional Comments From ananth at in dot ibm dot com  2007-04-18 04:50 -------
Subject: Re:  Problem in making kprobe modules portable across all the archtecture.

On Tue, Apr 17, 2007 at 04:27:38PM -0000, fche at redhat dot com wrote:
> 
> ------- Additional Comments From fche at redhat dot com  2007-04-17 17:27 -------
> Note that this would not fix systemtap, as we do not use the kprobes-level symbol
> lookup facilities.  It sounds like, for the PPC, systemtap itself should prefix
> function symbols with "." unconditionally, and not treat it as a conditional 
> fallback heuristic.

Yes, that would always work, but you may need to check the module:symbol
type address lookups.

That begs the question... till RHEL5, the compiler used in RHEL would
include both text and data symbols for powerpc. But, RHEL5 has some
compiler modifications that causes the data symbol (eg., "do_fork") to
be discarded and only the text symbol (".do_fork") is visible for
kallsyms lookup. Even upstream kernels built on RHEL5 have a similar
issue. Any specific reasons for this?


-- 


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

------- 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]