[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1313569203.4115.149.camel@minggr.sh.intel.com>
Date: Wed, 17 Aug 2011 16:20:03 +0800
From: Lin Ming <ming.m.lin@...el.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Andi Kleen <andi@...stfloor.org>,
"Huang, Ying" <ying.huang@...el.com>,
"He, Fan F" <fan.f.he@...el.com>
Subject: perf: problem of 32bit mmap call graph recording
Hi all,
On 32 bit machine, we have problem to get the usersapce call graph of
mmap syscall.
You can reproduce it with below command on 32bit machine.
sudo perf record -f -g -e raw_syscalls:sys_enter --filter "id==192" ls
sudo perf report |less
# Events: 26
#
# Overhead Command Shared Object Symbol
# ........ ....... ................. ......
#
100.00% ls [kernel.kallsyms] [k] syscall_trace_enter
|
--- syscall_trace_enter
syscall_trace_entry
|
|--88.46%-- __mmap <--- only __mmap, no more userspace call stacks
|
--11.54%-- 0xffffe424
Kernel relies on userspace bp register to get call graph information.
But for mmap syscall, the bp register is used to pass in the sixth
parameter(offset).
void *mmap(void *addr, size_t length, int prot, int flags,
int fd, off_t offset);
Anyway to fix this issue on 32bit machine?
Thanks,
Lin Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists