From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v4 0/6] Support perf -vv
Date: Fri, 30 Mar 2018 17:27:10 +0800 [thread overview]
Message-ID: <1522402036-22915-1-git-send-email-yao.jin@linux.intel.com> (raw)
We keep having bug reports that when users build perf on their own,
but they don't install some needed libraries such as libelf,
libbfd/libibery.
The perf can build, but it is missing important functionality. And
users may complain that perf has issue or bug.
This patch-set support to print the status of compiled-in libraries.
Once users think perf missing some functionality, it should be very
easy for them to check the libraries status.
For example:
$ ./perf version --build-options
or
./perf --version --build-options
or
./perf -v --build-options
or
./perf -vv
perf version 4.13.rc5.g6727c5
dwarf: [ on ] # HAVE_DWARF_SUPPORT
dwarf_getlocations: [ on ] # HAVE_DWARF_GETLOCATIONS_SUPPORT
glibc: [ on ] # HAVE_GLIBC_SUPPORT
gtk2: [ on ] # HAVE_GTK2_SUPPORT
libaudit: [ OFF ] # HAVE_LIBAUDIT_SUPPORT
libbfd: [ on ] # HAVE_LIBBFD_SUPPORT
libelf: [ on ] # HAVE_LIBELF_SUPPORT
libnuma: [ on ] # HAVE_LIBNUMA_SUPPORT
numa_num_possible_cpus: [ on ] # HAVE_LIBNUMA_SUPPORT
libperl: [ on ] # HAVE_LIBPERL_SUPPORT
libpython: [ on ] # HAVE_LIBPYTHON_SUPPORT
libslang: [ on ] # HAVE_SLANG_SUPPORT
libcrypto: [ on ] # HAVE_LIBCRYPTO_SUPPORT
libunwind: [ on ] # HAVE_LIBUNWIND_SUPPORT
libdw-dwarf-unwind: [ on ] # HAVE_DWARF_SUPPORT
zlib: [ on ] # HAVE_ZLIB_SUPPORT
lzma: [ on ] # HAVE_LZMA_SUPPORT
get_cpuid: [ on ] # HAVE_AUXTRACE_SUPPORT
bpf: [ on ] # HAVE_LIBBPF_SUPPORT
v4:
---
1. Also print the macro name. That would make it easier
to grep around in the source looking for where code
related a particular features is located.
2. Update since HAVE_DWARF_GETLOCATIONS is renamed to
HAVE_DWARF_GETLOCATIONS_SUPPORT
Patch impacted:
---------------
perf config: Rename to HAVE_DWARF_GETLOCATIONS_SUPPORT
perf version: Print the compiled-in status of libraries
others not changed
Jin Yao (5):
perf config: Add some new -DHAVE_XXX to CFLAGS
perf config: Rename to HAVE_DWARF_GETLOCATIONS_SUPPORT
perf version: Print the compiled-in status of libraries
perf: Support perf -vv
perf Documentation: Create perf-version.txt
Jiri Olsa (1):
tools include: Add config.h header file
tools/include/tools/config.h | 34 +++++++++++++
tools/perf/Documentation/perf-version.txt | 24 +++++++++
tools/perf/Makefile.config | 8 ++-
tools/perf/builtin-version.c | 82 ++++++++++++++++++++++++++++++-
tools/perf/perf.c | 6 +++
tools/perf/perf.h | 1 +
tools/perf/util/dwarf-aux.c | 2 +-
7 files changed, 154 insertions(+), 3 deletions(-)
create mode 100644 tools/include/tools/config.h
create mode 100644 tools/perf/Documentation/perf-version.txt
--
2.7.4
next reply other threads:[~2018-03-30 1:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 9:27 Jin Yao [this message]
2018-03-30 9:27 ` [PATCH v4 1/6] tools include: Add config.h header file Jin Yao
2018-04-04 5:30 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2018-03-30 9:27 ` [PATCH v4 3/6] perf config: Rename to HAVE_DWARF_GETLOCATIONS_SUPPORT Jin Yao
2018-04-04 5:31 ` [tip:perf/urgent] " tip-bot for Jin Yao
2018-03-30 9:27 ` [PATCH v4 4/6] perf version: Print the compiled-in status of libraries Jin Yao
2018-04-02 16:47 ` Arnaldo Carvalho de Melo
2018-04-03 1:24 ` Jin, Yao
2018-04-04 5:31 ` [tip:perf/urgent] " tip-bot for Jin Yao
2018-03-30 9:27 ` [PATCH v4 5/6] perf: Support perf -vv Jin Yao
2018-04-04 5:32 ` [tip:perf/urgent] perf tools: Add 'perf -vv' as an alias to 'perf version --build-options' tip-bot for Jin Yao
2018-03-30 9:27 ` [PATCH v4 6/6] perf Documentation: Create perf-version.txt Jin Yao
2018-04-04 5:32 ` [tip:perf/urgent] perf version: Add man page tip-bot for Jin Yao
2018-03-30 9:34 ` [PATCH v4 0/6] Support perf -vv 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=1522402036-22915-1-git-send-email-yao.jin@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=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