[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160715161548.c60921b5fae817a19a1a7f80@kernel.org>
Date: Fri, 15 Jul 2016 16:15:48 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Daniel Bristot de Oliveira <daniel@...stot.me>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: perf probe -F with wildcards
Hi Arnaldo,
On Thu, 14 Jul 2016 21:16:41 -0300
Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> Hi Masami,
>
> I think this worked at some point?
>
> [root@...et acme]# perf probe -F | tail
> zswap_frontswap_init
> zswap_frontswap_invalidate_area
> zswap_frontswap_invalidate_page
> zswap_frontswap_load
> zswap_frontswap_store
> zswap_pool_create
> zswap_pool_current
> zswap_update_total_size
> zswap_writeback_entry
> zswap_zpool_param_set
> [root@...et acme]# perf probe -F rt_sp*
> no symbols found in [kernel.kallsyms], maybe install a debug package?
> Failed to load symbols in kernel
It seems that 2 problems we have,
- There is no function which starts with rt_sp.
- The error message is not good for that.
If you try perf probe -F acpi_*, you'll see a list of functions.
> [root@...et acme]# perf probe -F rt_sp\*
> no symbols found in [kernel.kallsyms], maybe install a debug package?
> Failed to load symbols in kernel
So, yeah, it should check symbol loading is really failed and should be
changed as "no symbols match to given filter" etc.
Thank you,
> [root@...et acme]#
>
>
> I.e. the second message is misleading :-\
>
> - Arnaldo
>
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists