[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lhnqw543.fsf@sejong.aot.lge.com>
Date: Wed, 05 Nov 2014 15:09:32 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
srikar@...ux.vnet.ibm.com, Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Brendan Gregg <brendan.gregg@...il.com>,
yrl.pp-manager.tt@...achi.com,
Hemant Kumar <hemant@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH perf/core 0/6] perf-probe: Bugfix and add new options for cache
Hi Masami,
On Tue, 04 Nov 2014 14:44:28 +0900, Masami Hiramatsu wrote:
> (2014/11/04 12:14), Namhyung Kim wrote:
>> Hi Masami,
>>
>> On Fri, 31 Oct 2014 14:51:29 -0400, Masami Hiramatsu wrote:
>>> So by using all of them, we can make an "event cache" file on all
>>> functions (except for inlined functions) as below.
>>>
>>> # perf probe --max-probes=100000 --no-inlines -a '* $params' -o event.cache
>>>
>>> builds "event.cache" file in which event settings for
>>> all function entries, like below;
>>>
>>> p:probe/reset_early_page_tables _text+12980741
>>> p:probe/copy_bootdata _text+12980830 real_mode_data=%di:u64
>>> p:probe/exit_amd_microcode _text+14692680
>>> p:probe/early_make_pgtable _text+12981274 address=%di:u64
>>> p:probe/x86_64_start_reservations _text+12981700 real_mode_data=%di:u64
>>> p:probe/x86_64_start_kernel _text+12981744 real_mode_data=%di:u64
>>> p:probe/reserve_ebda_region _text+12982117
>>
>> Does this event cache support kernel modules too? AFAIK it can have a
>> different address whenever loaded even on a same kernel.
>
> Yes, for the modules perf probe uses target function symbol directly instead
> of _text.
>
> ----
> perf probe -m xfs -o - -q -a xfs_acl_exists
> p:probe/xfs_acl_exists xfs:xfs_acl_exists+0
> ----
Ah, great! :)
Thanks,
Namhyung
--
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