All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Andi Kleen <andi@firstfloor.org>,
	"Huang, Ying" <ying.huang@intel.com>,
	"He, Fan F" <fan.f.he@intel.com>
Subject: perf: problem of 32bit mmap call graph recording
Date: Wed, 17 Aug 2011 16:20:03 +0800	[thread overview]
Message-ID: <1313569203.4115.149.camel@minggr.sh.intel.com> (raw)

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


             reply	other threads:[~2011-08-17  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17  8:20 Lin Ming [this message]
2011-08-17 13:19 ` perf: problem of 32bit mmap call graph recording Frederic Weisbecker

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=1313569203.4115.149.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=acme@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=fan.f.he@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.