From: "ananth at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/4384] Problem in making kprobe modules portable across all the archtecture.
Date: Wed, 18 Apr 2007 03:50:00 -0000 [thread overview]
Message-ID: <20070418035034.7583.qmail@sourceware.org> (raw)
In-Reply-To: <20070417132651.4384.srinivasa@in.ibm.com>
------- 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.
next prev parent reply other threads:[~2007-04-18 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 12:27 [Bug kprobes/4384] New: " srinivasa at in dot ibm dot com
2007-04-17 12:29 ` [Bug kprobes/4384] " srinivasa at in dot ibm dot com
2007-04-17 14:43 ` ananth at in dot ibm dot com
2007-04-17 16:27 ` fche at redhat dot com
2007-04-18 3:50 ` ananth at in dot ibm dot com [this message]
2007-04-18 4:18 ` ananth at in dot ibm dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070418035034.7583.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).