From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/4384] New: Problem in making kprobe modules portable across all the archtecture.
Date: Tue, 17 Apr 2007 12:27:00 -0000 [thread overview]
Message-ID: <20070417132651.4384.srinivasa@in.ibm.com> (raw)
When data symbols are not present in kernel image, one has to add dot(".")
before function name, that he wants to probe in kprobe module on ppc64.
Hence kernel module may not become portable across all the architecture.
When data symbols are missing on ppc64,
====================
[root@llm27lp1 ~]# cat /proc/kallsyms | grep do_fork
c00000000006283c T .do_fork
==============================
kp.symbol_name = ".do_fork";
============================
But if data symbols were included, then it looks like this
================
llm27lp2:~ # cat /proc/kallsyms |grep do_fork
c00000000005de28 T .do_fork
c0000000005fbe88 D do_fork
======================
kp.symbol_name = ".do_fork";
===============================
Iam attaching patch here, which solves this problem. Please let me know your
comments on this.
Thanks
Srinivasa DS
--
Summary: Problem in making kprobe modules portable across all the
archtecture.
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: kprobes
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: srinivasa at in dot ibm dot com
CC: ananth at in dot ibm dot com,anil dot s dot
keshavamurthy at intel dot com,jkenisto at us dot ibm
dot com,prasanna at in dot ibm dot com
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 reply other threads:[~2007-04-17 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 12:27 srinivasa at in dot ibm dot com [this message]
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
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=20070417132651.4384.srinivasa@in.ibm.com \
--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).