From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1698 invoked by alias); 17 Apr 2007 12:27:06 -0000 Received: (qmail 1634 invoked by uid 48); 17 Apr 2007 12:26:51 -0000 Date: Tue, 17 Apr 2007 12:27:00 -0000 From: "srinivasa at in dot ibm dot com" To: systemtap@sources.redhat.com Message-ID: <20070417132651.4384.srinivasa@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug kprobes/4384] New: Problem in making kprobe modules portable across all the archtecture. X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00075.txt.bz2 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.