[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D078037.9060207@cisco.com>
Date: Tue, 14 Dec 2010 07:33:27 -0700
From: "David S. Ahern" <daahern@...co.com>
To: Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC: linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] perf tools: Add symfs option for off-box analysis
using specified tree
On 12/14/10 07:06, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 14, 2010 at 10:52:45AM -0200, Arnaldo Carvalho de Melo escreveu:
>> Ok, there are still some problems:
>>
>> It is escaping the symfs jail for /home/acme/bin/perf, /lib64/libpthread-2.5.so
>> and kernel modules, investigating...
>
> Those 'G' signals means DSO__ORIG_GUEST_KMODULE, since you were not
> prefixing that case with symfs, it was the jail leak point, fixed, doing
> some more testing before merging.
yuk. I did not touch the hypervisor paths.
So the 'guest' route is tried all the time because of the origin list --
even when it's not applicable.
David
>
>> [acme@...a linux]$ find /tmp/bla
>> /tmp/bla
>> /tmp/bla/lib64
>> /tmp/bla/lib64/libc-2.5.so
>> [acme@...a linux]$ perf report -v -g none --stdio --symfs /tmp/bla
>> Failed to open [kernel.kallsyms], continuing without symbols
>> # Events: 503 cycles
>> #
>> # Overhead Command Shared Object Symbol
>> # ........ .......... ..................................... ....................
>> #
>> 0.84% perf /home/acme/bin/perf 0x26bf1 G [.] die_builtin
>> 0.21% perf /home/acme/bin/perf 0x1db4b G [.] event__synthesize_kernel_mmap
>> 0.21% perf /home/acme/bin/perf 0x4700 G [.] _init
>> 0.21% perf /home/acme/bin/perf 0x1deca G [.] event__synthesize_comm
>> 0.21% perf /lib64/libpthread-2.5.so 0xd210 G [.] __write_nocancel
>> 0.21% perf /home/acme/bin/perf 0xddbd G [.] atexit_header
>> 0.03% kworker/0:1 /lib/modules/2.6.37-rc3/.../ixgbe.ko 0x605 G [k] ixgbe_update_stats
--
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