From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH] perf util: Display warning when perf report/annotate is missing some libs
Date: Fri, 12 Jan 2018 10:22:29 +0800 [thread overview]
Message-ID: <ef52d9de-54b6-88a6-625d-bd048a098222@linux.intel.com> (raw)
In-Reply-To: <20180111153028.GB20406@krava>
On 1/11/2018 11:30 PM, Jiri Olsa wrote:
> On Thu, Jan 11, 2018 at 07:03:06PM +0800, Jin Yao wrote:
>> We keep having bug reports that when users build perf on their own,
>
> we already have same warnings during the build
>
Yes, there will be warnings displayed during the build if some libraries
are missing.
While I do find the users (especially the new perf user) don't notice
the warning. They only care about the success of build.
Once they use this perf version and find something working strangely,
they will say that perf may have bug. :(
>> but they don't install some needed libraries like libelf, libbfd/libibery.
>
> how about saying that in the symbol column,
> instead of poluting report's output, like:
>
> $ perf report --stdio
>
> # Overhead Command Shared Object Symbol (disabled)
> # ........ ....... ................ ......................
>
I just think it'd better provide some hints to user. For example,
"symbol is disabled and you need to install libelf/xxx", say something
like that.
But it looks the column can't contain too much information (i.e. no more
space to contain the entire hints).
Any idea? Or just add this warning in verbose mode?
> also your change does not affect tui mode
>
> annotation for some reason does not start at all.. could be
> little more verbose ;-)
>
> jirka
>
Yes, it doesn't affect tui mode.
Or we just add this warning in verbose mode?
e.g. perf report -v?
Thanks
Jin Yao
next prev parent reply other threads:[~2018-01-12 2:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 11:03 Jin Yao
2018-01-11 15:30 ` Jiri Olsa
2018-01-12 2:22 ` Jin, Yao [this message]
2018-03-21 2:11 ` Jin, Yao
2018-03-21 15:38 ` Jiri Olsa
2018-03-21 15:40 ` Arnaldo Carvalho de Melo
2018-03-21 15:43 ` Arnaldo Carvalho de Melo
2018-03-21 15:45 ` Arnaldo Carvalho de Melo
2018-03-21 16:04 ` Jiri Olsa
2018-03-21 18:52 ` Arnaldo Carvalho de Melo
2018-03-21 19:02 ` Jiri Olsa
2018-03-22 1:31 ` Jin, Yao
2018-03-22 1:04 ` Jin, Yao
2018-03-22 8:51 ` Jiri Olsa
2018-03-23 3:09 ` Jin, Yao
2018-03-23 14:50 ` Arnaldo Carvalho de Melo
2018-03-23 15:17 ` Jiri Olsa
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=ef52d9de-54b6-88a6-625d-bd048a098222@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome