2010-03-28 01:30:45 +08:00
i f e q ( "$(origin O)" , "command line" )
OUTPUT := $( O) /
e n d i f
2009-04-20 19:32:07 +08:00
# The default target of this Makefile is...
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
all :
2009-03-24 04:29:59 +08:00
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
i n c l u d e c o n f i g / u t i l i t i e s . m a k
2010-08-19 00:32:37 +08:00
i f n e q ( $( OUTPUT ) , )
# check that the output directory actually exists
OUTDIR := $( shell cd $( OUTPUT) && /bin/pwd)
$( if $ ( OUTDIR ) ,, $ ( error output directory "$ ( OUTPUT ) " does not exist ) )
e n d i f
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
# Define V to have a more verbose compile.
2009-04-20 19:32:07 +08:00
#
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
# Define PYTHON to point to the python binary if the default
# `python' is not correct; for example: PYTHON=python2
#
# Define PYTHON_CONFIG to point to the python-config binary if
# the default `$(PYTHON)-config' is not correct.
#
2009-04-20 19:32:07 +08:00
# Define ASCIIDOC8 if you want to format documentation with AsciiDoc 8
#
# Define DOCBOOK_XSL_172 if you want to format man pages with DocBook XSL v1.72.
#
2009-10-29 23:20:02 +08:00
# Define LDFLAGS=-static to build a static binary.
2009-11-22 20:13:35 +08:00
#
# Define EXTRA_CFLAGS=-m64 or EXTRA_CFLAGS=-m32 as appropriate for cross-builds.
2010-03-23 00:10:27 +08:00
#
# Define NO_DWARF if you do not want debug-info analysis feature at all.
2011-09-09 04:42:39 +08:00
#
# Define WERROR=0 to disable treating any warnings as errors.
2009-03-24 04:29:59 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)PERF-VERSION-FILE : .FORCE -PERF -VERSION -FILE
@$( SHELL_PATH) util/PERF-VERSION-GEN $( OUTPUT)
- i n c l u d e $( OUTPUT ) P E R F - V E R S I O N - F I L E
2009-03-24 04:29:59 +08:00
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
uname_M := $( shell uname -m 2>/dev/null || echo not)
2009-04-08 21:01:31 +08:00
2010-04-20 14:58:32 +08:00
ARCH ?= $( shell echo $( uname_M) | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
-e s/arm.*/arm/ -e s/sa110/arm/ \
-e s/s390x/s390/ -e s/parisc64/parisc/ \
-e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
-e s/sh[ 234] .*/sh/ )
2011-05-07 12:41:14 +08:00
CC = $( CROSS_COMPILE) gcc
AR = $( CROSS_COMPILE) ar
2010-04-20 14:58:32 +08:00
# Additional ARCH settings for x86
i f e q ( $( ARCH ) , i 3 8 6 )
ARCH := x86
e n d i f
i f e q ( $( ARCH ) , x 8 6 _ 6 4 )
2011-05-07 12:41:14 +08:00
ARCH := x86
2011-07-12 05:38:24 +08:00
IS_X86_64 := 0
ifeq ( , $( findstring m32,$( EXTRA_CFLAGS) ) )
IS_X86_64 := $( shell echo __x86_64__ | ${ CC } -E -xc - | tail -n 1)
endif
2011-05-07 12:41:14 +08:00
ifeq ( ${ IS_X86_64 } , 1)
RAW_ARCH := x86_64
ARCH_CFLAGS := -DARCH_X86_64
ARCH_INCLUDE = ../../arch/x86/lib/memcpy_64.S
endif
2010-04-20 14:58:32 +08:00
e n d i f
2011-09-09 04:42:39 +08:00
# Treat warnings as errors unless directed not to
i f n e q ( $( WERROR ) , 0 )
CFLAGS_WERROR := -Werror
e n d i f
2009-08-15 18:26:57 +08:00
#
# Include saner warnings here, which can catch bugs:
#
2009-09-02 20:50:23 +08:00
2009-10-26 13:40:01 +08:00
EXTRA_WARNINGS := -Wformat
2009-09-02 20:50:23 +08:00
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wformat-security
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wformat-y2k
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wshadow
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Winit-self
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wpacked
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wredundant-decls
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wstrict-aliasing= 3
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wswitch-default
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wswitch-enum
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wno-system-headers
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wundef
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wwrite-strings
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wbad-function-cast
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wmissing-declarations
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wmissing-prototypes
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wnested-externs
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wold-style-definition
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wstrict-prototypes
EXTRA_WARNINGS := $( EXTRA_WARNINGS) -Wdeclaration-after-statement
2009-08-15 18:26:57 +08:00
2009-10-21 07:19:34 +08:00
i f e q ( "$(origin DEBUG)" , "command line" )
PERF_DEBUG = $( DEBUG)
e n d i f
i f n d e f P E R F _ D E B U G
CFLAGS_OPTIMIZE = -O6
e n d i f
2011-09-09 04:42:39 +08:00
CFLAGS = -fno-omit-frame-pointer -ggdb3 -Wall -Wextra -std= gnu99 $( CFLAGS_WERROR) $( CFLAGS_OPTIMIZE) -D_FORTIFY_SOURCE= 2 $( EXTRA_WARNINGS) $( EXTRA_CFLAGS)
2009-10-29 23:20:02 +08:00
EXTLIBS = -lpthread -lrt -lelf -lm
2010-03-30 00:47:55 +08:00
ALL_CFLAGS = $( CFLAGS) -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS= 64
2009-04-20 19:32:07 +08:00
ALL_LDFLAGS = $( LDFLAGS)
STRIP ?= strip
# Among the variables below, these:
2009-04-20 21:00:56 +08:00
# perfexecdir
2009-04-20 19:32:07 +08:00
# template_dir
# mandir
# infodir
# htmldir
2009-04-20 21:00:56 +08:00
# ETC_PERFCONFIG (but not sysconfdir)
2009-04-20 19:32:07 +08:00
# can be specified as a relative path some/where/else;
2009-04-20 21:00:56 +08:00
# this is interpreted as relative to $(prefix) and "perf" at
2009-04-20 19:32:07 +08:00
# runtime figures out where they are based on the path to the executable.
# This can help installing the suite in a relocatable way.
2010-03-11 20:57:00 +08:00
# Make the path relative to DESTDIR, not to prefix
i f n d e f D E S T D I R
2009-04-20 19:32:07 +08:00
prefix = $( HOME)
2010-03-11 20:57:00 +08:00
e n d i f
2009-04-20 19:32:07 +08:00
bindir_relative = bin
bindir = $( prefix) /$( bindir_relative)
mandir = share/man
infodir = share/info
2009-04-20 21:00:56 +08:00
perfexecdir = libexec/perf-core
2009-04-20 19:32:07 +08:00
sharedir = $( prefix) /share
2009-04-20 21:00:56 +08:00
template_dir = share/perf-core/templates
htmldir = share/doc/perf-doc
2009-04-20 19:32:07 +08:00
i f e q ( $( prefix ) , / u s r )
sysconfdir = /etc
2009-04-20 21:00:56 +08:00
ETC_PERFCONFIG = $( sysconfdir) /perfconfig
2009-04-20 19:32:07 +08:00
e l s e
sysconfdir = $( prefix) /etc
2009-04-20 21:00:56 +08:00
ETC_PERFCONFIG = etc/perfconfig
2009-04-20 19:32:07 +08:00
e n d i f
lib = lib
export prefix bindir sharedir sysconfdir
RM = rm -f
2010-08-17 23:22:08 +08:00
MKDIR = mkdir
2009-04-20 19:32:07 +08:00
FIND = find
INSTALL = install
# sparse is architecture-neutral, which means that we need to tell it
# explicitly what architecture to check for. Fix this up for yours..
SPARSE_FLAGS = -D__BIG_ENDIAN__ -D__powerpc__
2011-04-13 04:30:13 +08:00
- i n c l u d e c o n f i g / f e a t u r e - t e s t s . m a k
2010-01-12 18:58:30 +08:00
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
i f e q ( $( call try -cc ,$ ( SOURCE_HELLO ) ,-Werror -fstack -protector -all ) , y )
CFLAGS := $( CFLAGS) -fstack-protector-all
2009-11-11 15:43:03 +08:00
e n d i f
2009-04-20 19:32:07 +08:00
2011-01-23 05:29:53 +08:00
i f e q ( $( call try -cc ,$ ( SOURCE_HELLO ) ,-Werror -Wstack -protector ) , y )
CFLAGS := $( CFLAGS) -Wstack-protector
e n d i f
i f e q ( $( call try -cc ,$ ( SOURCE_HELLO ) ,-Werror -Wvolatile -register -var ) , y )
CFLAGS := $( CFLAGS) -Wvolatile-register-var
e n d i f
2009-04-20 19:32:07 +08:00
### --- END CONFIGURATION SECTION ---
# Those must not be GNU-specific; they are shared with perl/ which may
# be built by a different compiler. (Note that this is an artifact now
# but it still might be nice to keep that distinction.)
2010-04-20 14:58:32 +08:00
BASIC_CFLAGS = -Iutil/include -Iarch/$( ARCH) /include
2009-04-20 19:32:07 +08:00
BASIC_LDFLAGS =
# Guard against environment variables
BUILTIN_OBJS =
LIB_H =
LIB_OBJS =
perf tools: Initial python binding
First clarifying that this kind of binding is not a replacement or an
equivalent to the 'perf script' way of using python with perf.
The 'perf script' way is to process events and look at a given script
for some python function that matches the events to pass each event for
processing.
This is a python module, i.e. everything is driven from the python
script, that merely uses "import perf" or "from perf import".
perf script is focused on tracepoints, this binding is focused on profiling as
an initial target. More work is needed to make available tracepoint specific
variables as event variables accessible via this binding.
There is one example of such usage model, in
tools/perf/python/twatch.py, a tool to watch "cycles" events together
with task (fork, exit) and comm perf events.
For now, due to me not being able to grok how python distutils cope with
building C extensions outside the sources dir the install target just
builds it, I'm using it as:
[root@emilia linux]# export PYTHONPATH=~acme/git/build/perf/lib.linux-x86_64-2.6/
[root@emilia linux]# tools/perf/python/twatch.py
cpu: 4, pid: 30126, tid: 30126 { type: mmap, pid: 30126, tid: 30126, start: 0x4, length: 0x82e9ca03, offset: 0, filename: }
cpu: 6, pid: 47, tid: 47 { type: mmap, pid: 47, tid: 47, start: 0x6, length: 0xbef87c36, offset: 0, filename: }
cpu: 1, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0x1, length: 0x775d1904, offset: 0, filename: }
cpu: 7, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0x7, length: 0xc750aeb6, offset: 0, filename: }
cpu: 5, pid: 2255, tid: 2255 { type: mmap, pid: 2255, tid: 2255, start: 0x5, length: 0x76669635, offset: 0, filename: }
cpu: 0, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0, length: 0x6422ef6b, offset: 0, filename: }
cpu: 2, pid: 2255, tid: 2255 { type: mmap, pid: 2255, tid: 2255, start: 0x2, length: 0xe078757a, offset: 0, filename: }
cpu: 1, pid: 5769, tid: 5769 { type: fork, pid: 30127, ppid: 5769, tid: 30127, ptid: 5769, time: 103893991270534}
cpu: 6, pid: 30127, tid: 30127 { type: comm, pid: 30127, tid: 30127, comm: ls }
cpu: 6, pid: 30127, tid: 30127 { type: exit, pid: 30127, ppid: 30127, tid: 30127, ptid: 30127, time: 103893993273024}
The first 8 mmap events in this 8 way machine are a mistery that is still being
investigated.
More of the tools/perf/util/ APIs will be exposed via this python binding as
the need arises. For now the focus is on creating events and processing them,
symbol resolution is an obvious next step, with tracepoint variables as a close
second step.
Cc: Clark Williams <williams@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-01-30 01:44:29 +08:00
PYRF_OBJS =
2009-04-20 19:32:07 +08:00
SCRIPT_SH =
2010-01-15 23:17:52 +08:00
SCRIPT_SH += perf-archive.sh
2009-04-20 21:00:56 +08:00
2010-08-24 13:23:50 +08:00
grep-libs = $( filter -l%,$( 1) )
strip-libs = $( filter-out -l%,$( 1) )
perf tools: Remove verbose build messages for the python binding
Also now it builds it in a well known location:
[acme@felicio linux]$ rm -rf ../build/perf/
[acme@felicio linux]$ mkdir ../build/perf
[acme@felicio linux]$ make -j2 O=~acme/git/build/perf -C tools/perf/
<SNIP>
[acme@felicio linux]$ ls -la ../build/perf/python/
total 152
-rwxrwxr-x 1 acme acme 147957 Feb 1 14:56 perf.so
drwxrwxr-x 3 acme acme 17 Feb 1 14:56 temp
[acme@felicio linux]$
[root@felicio ~]# strip ~acme/git/build/perf/python/perf.so
[root@felicio ~]# ls -la ~acme/git/build/perf/python/perf.so
-rwxrwxr-x 1 acme acme 46264 Feb 1 14:58 /home/acme/git/build/perf/python/perf.so
[root@felicio ~]# export PYTHONPATH=~acme/git/build/perf/python/
[root@felicio ~]# ~acme/git/linux/tools/perf/python/twatch.py
cpu: 0, pid: 7751, tid: 7751 { type: exit, pid: 7751, ppid: 7751, tid: 7751, ptid: 7751, time: 54562393512356}
cpu: 0, pid: 13700, tid: 13700 { type: fork, pid: 7756, ppid: 13700, tid: 7756, ptid: 13700, time: 54562393746739}
cpu: 1, pid: 7756, tid: 7756 { type: fork, pid: 7757, ppid: 7756, tid: 7757, ptid: 7756, time: 54562394246152}
cpu: 1, pid: 7757, tid: 7757 { type: comm, pid: 7757, tid: 7757, comm: awk }
cpu: 1, pid: 7757, tid: 7757 { type: exit, pid: 7757, ppid: 7757, tid: 7757, ptid: 7757, time: 54562395456813}
Reported-by: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-02 00:57:02 +08:00
$(OUTPUT)python/perf.so : $( PYRF_OBJS )
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
$( QUIET_GEN) CFLAGS = '$(BASIC_CFLAGS)' $( PYTHON_WORD) util/setup.py \
2011-07-22 19:33:07 +08:00
--quiet build_ext; \
mkdir -p $( OUTPUT) python && \
cp $( PYTHON_EXTBUILD_LIB) perf.so $( OUTPUT) python/
2009-04-20 21:00:56 +08:00
#
# No Perl scripts right now:
#
2011-02-03 02:04:27 +08:00
SCRIPTS = $( patsubst %.sh,%,$( SCRIPT_SH) )
2009-04-20 19:32:07 +08:00
2009-04-20 21:00:56 +08:00
#
2009-04-20 22:13:46 +08:00
# Single 'perf' binary right now:
2009-04-20 21:00:56 +08:00
#
2010-03-28 01:30:45 +08:00
PROGRAMS += $( OUTPUT) perf
2009-04-20 19:32:07 +08:00
2011-02-02 02:40:51 +08:00
LANG_BINDINGS =
perf tools: Remove verbose build messages for the python binding
Also now it builds it in a well known location:
[acme@felicio linux]$ rm -rf ../build/perf/
[acme@felicio linux]$ mkdir ../build/perf
[acme@felicio linux]$ make -j2 O=~acme/git/build/perf -C tools/perf/
<SNIP>
[acme@felicio linux]$ ls -la ../build/perf/python/
total 152
-rwxrwxr-x 1 acme acme 147957 Feb 1 14:56 perf.so
drwxrwxr-x 3 acme acme 17 Feb 1 14:56 temp
[acme@felicio linux]$
[root@felicio ~]# strip ~acme/git/build/perf/python/perf.so
[root@felicio ~]# ls -la ~acme/git/build/perf/python/perf.so
-rwxrwxr-x 1 acme acme 46264 Feb 1 14:58 /home/acme/git/build/perf/python/perf.so
[root@felicio ~]# export PYTHONPATH=~acme/git/build/perf/python/
[root@felicio ~]# ~acme/git/linux/tools/perf/python/twatch.py
cpu: 0, pid: 7751, tid: 7751 { type: exit, pid: 7751, ppid: 7751, tid: 7751, ptid: 7751, time: 54562393512356}
cpu: 0, pid: 13700, tid: 13700 { type: fork, pid: 7756, ppid: 13700, tid: 7756, ptid: 13700, time: 54562393746739}
cpu: 1, pid: 7756, tid: 7756 { type: fork, pid: 7757, ppid: 7756, tid: 7757, ptid: 7756, time: 54562394246152}
cpu: 1, pid: 7757, tid: 7757 { type: comm, pid: 7757, tid: 7757, comm: awk }
cpu: 1, pid: 7757, tid: 7757 { type: exit, pid: 7757, ppid: 7757, tid: 7757, ptid: 7757, time: 54562395456813}
Reported-by: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-02 00:57:02 +08:00
2009-04-20 21:00:56 +08:00
# what 'all' will build and 'install' will install, in perfexecdir
2011-02-02 02:40:51 +08:00
ALL_PROGRAMS = $( PROGRAMS) $( SCRIPTS)
2009-04-20 19:32:07 +08:00
2009-04-20 21:00:56 +08:00
# what 'all' will build but not install in perfexecdir
2011-02-03 01:57:41 +08:00
OTHER_PROGRAMS = $( OUTPUT) perf
2009-04-20 19:32:07 +08:00
# Set paths to tools early so that they can be used for version tests.
i f n d e f S H E L L _ P A T H
SHELL_PATH = /bin/sh
e n d i f
i f n d e f P E R L _ P A T H
PERL_PATH = /usr/bin/perl
e n d i f
export PERL_PATH
2010-03-28 01:30:45 +08:00
LIB_FILE = $( OUTPUT) libperf.a
2009-04-20 21:00:56 +08:00
perf: Do the big rename: Performance Counters -> Performance Events
Bye-bye Performance Counters, welcome Performance Events!
In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.
Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.
All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)
The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.
Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.
User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)
This patch has been generated via the following script:
FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')
sed -i \
-e 's/PERF_EVENT_/PERF_RECORD_/g' \
-e 's/PERF_COUNTER/PERF_EVENT/g' \
-e 's/perf_counter/perf_event/g' \
-e 's/nb_counters/nb_events/g' \
-e 's/swcounter/swevent/g' \
-e 's/tpcounter_event/tp_event/g' \
$FILES
for N in $(find . -name perf_counter.[ch]); do
M=$(echo $N | sed 's/perf_counter/perf_event/g')
mv $N $M
done
FILES=$(find . -name perf_event.*)
sed -i \
-e 's/COUNTER_MASK/REG_MASK/g' \
-e 's/COUNTER/EVENT/g' \
-e 's/\<event\>/event_id/g' \
-e 's/counter/event/g' \
-e 's/Counter/Event/g' \
$FILES
... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.
Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.
( NOTE: 'counters' are still the proper terminology when we deal
with hardware registers - and these sed scripts are a bit
over-eager in renaming them. I've undone some of that, but
in case there's something left where 'counter' would be
better than 'event' we can undo that on an individual basis
instead of touching an otherwise nicely automated patch. )
Suggested-by: Stephane Eranian <eranian@google.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Paul Mackerras <paulus@samba.org>
Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-arch@vger.kernel.org>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-09-21 18:02:48 +08:00
LIB_H += ../../include/linux/perf_event.h
2009-07-01 23:28:37 +08:00
LIB_H += ../../include/linux/rbtree.h
2009-07-02 01:46:08 +08:00
LIB_H += ../../include/linux/list.h
2011-05-26 21:13:38 +08:00
LIB_H += ../../include/linux/const.h
2010-01-30 19:43:24 +08:00
LIB_H += ../../include/linux/hash.h
2009-10-17 08:08:18 +08:00
LIB_H += ../../include/linux/stringify.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/linux/bitmap.h
LIB_H += util/include/linux/bitops.h
LIB_H += util/include/linux/compiler.h
2011-05-26 21:13:38 +08:00
LIB_H += util/include/linux/const.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/linux/ctype.h
LIB_H += util/include/linux/kernel.h
2009-07-02 01:46:08 +08:00
LIB_H += util/include/linux/list.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/linux/module.h
LIB_H += util/include/linux/poison.h
LIB_H += util/include/linux/prefetch.h
LIB_H += util/include/linux/rbtree.h
2009-10-20 01:11:36 +08:00
LIB_H += util/include/linux/string.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/linux/types.h
2010-11-25 15:04:53 +08:00
LIB_H += util/include/linux/linkage.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/asm/asm-offsets.h
2009-12-28 07:36:58 +08:00
LIB_H += util/include/asm/bug.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/asm/byteorder.h
2010-05-01 06:31:12 +08:00
LIB_H += util/include/asm/hweight.h
2009-10-20 01:31:31 +08:00
LIB_H += util/include/asm/swab.h
LIB_H += util/include/asm/system.h
LIB_H += util/include/asm/uaccess.h
2010-04-20 14:58:32 +08:00
LIB_H += util/include/dwarf-regs.h
2010-11-25 15:04:53 +08:00
LIB_H += util/include/asm/dwarf2.h
LIB_H += util/include/asm/cpufeature.h
2009-05-02 00:29:57 +08:00
LIB_H += perf.h
2011-02-04 19:45:46 +08:00
LIB_H += util/annotate.h
2009-12-28 07:36:58 +08:00
LIB_H += util/cache.h
LIB_H += util/callchain.h
2010-02-04 02:52:04 +08:00
LIB_H += util/build-id.h
2009-12-28 07:36:58 +08:00
LIB_H += util/debug.h
2009-11-08 23:01:37 +08:00
LIB_H += util/debugfs.h
2009-10-04 07:30:48 +08:00
LIB_H += util/event.h
2011-01-04 02:39:04 +08:00
LIB_H += util/evsel.h
2011-01-12 06:56:53 +08:00
LIB_H += util/evlist.h
2009-12-28 07:36:58 +08:00
LIB_H += util/exec_cmd.h
2009-06-25 23:05:54 +08:00
LIB_H += util/types.h
2009-04-27 14:02:14 +08:00
LIB_H += util/levenshtein.h
2009-12-28 07:37:00 +08:00
LIB_H += util/map.h
2009-04-27 14:02:14 +08:00
LIB_H += util/parse-options.h
2009-05-26 17:10:09 +08:00
LIB_H += util/parse-events.h
2009-04-27 14:02:14 +08:00
LIB_H += util/quote.h
LIB_H += util/util.h
2011-01-04 02:39:04 +08:00
LIB_H += util/xyarray.h
2009-12-12 07:24:02 +08:00
LIB_H += util/header.h
2009-04-27 14:02:14 +08:00
LIB_H += util/help.h
2009-12-12 07:24:02 +08:00
LIB_H += util/session.h
2009-04-27 14:02:14 +08:00
LIB_H += util/strbuf.h
2009-07-01 06:01:20 +08:00
LIB_H += util/strlist.h
2011-01-20 22:15:30 +08:00
LIB_H += util/strfilter.h
2009-12-28 07:36:58 +08:00
LIB_H += util/svghelper.h
2011-11-28 18:30:20 +08:00
LIB_H += util/tool.h
2009-04-27 14:02:14 +08:00
LIB_H += util/run-command.h
2009-05-27 15:50:13 +08:00
LIB_H += util/sigchain.h
2009-05-29 01:55:04 +08:00
LIB_H += util/symbol.h
2009-06-04 21:19:47 +08:00
LIB_H += util/color.h
2009-08-07 19:55:24 +08:00
LIB_H += util/values.h
2009-09-25 00:02:49 +08:00
LIB_H += util/sort.h
2009-09-28 21:32:55 +08:00
LIB_H += util/hist.h
2009-09-29 01:48:46 +08:00
LIB_H += util/thread.h
2011-01-19 01:15:24 +08:00
LIB_H += util/thread_map.h
2009-12-28 07:36:58 +08:00
LIB_H += util/trace-event.h
2009-12-01 08:19:34 +08:00
LIB_H += util/probe-finder.h
2011-06-27 15:27:27 +08:00
LIB_H += util/dwarf-aux.h
2009-12-01 08:19:58 +08:00
LIB_H += util/probe-event.h
2010-05-15 07:05:21 +08:00
LIB_H += util/pstack.h
perf tools: Fix sparse CPU numbering related bugs
At present, the perf subcommands that do system-wide monitoring
(perf stat, perf record and perf top) don't work properly unless
the online cpus are numbered 0, 1, ..., N-1. These tools ask
for the number of online cpus with sysconf(_SC_NPROCESSORS_ONLN)
and then try to create events for cpus 0, 1, ..., N-1.
This creates problems for systems where the online cpus are
numbered sparsely. For example, a POWER6 system in
single-threaded mode (i.e. only running 1 hardware thread per
core) will have only even-numbered cpus online.
This fixes the problem by reading the /sys/devices/system/cpu/online
file to find out which cpus are online. The code that does that is in
tools/perf/util/cpumap.[ch], and consists of a read_cpu_map()
function that sets up a cpumap[] array and returns the number of
online cpus. If /sys/devices/system/cpu/online can't be read or
can't be parsed successfully, it falls back to using sysconf to
ask how many cpus are online and sets up an identity map in cpumap[].
The perf record, perf stat and perf top code then calls
read_cpu_map() in the system-wide monitoring case (instead of
sysconf) and uses cpumap[] to get the cpu numbers to pass to
perf_event_open.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Cc: Anton Blanchard <anton@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>
LKML-Reference: <20100310093609.GA3959@brick.ozlabs.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2010-03-10 17:36:09 +08:00
LIB_H += util/cpumap.h
2011-02-01 00:50:39 +08:00
LIB_H += util/top.h
2010-11-25 15:04:53 +08:00
LIB_H += $( ARCH_INCLUDE)
perf tool: Add cgroup support
This patch adds the ability to filter monitoring based on container groups
(cgroups) for both perf stat and perf record. It is possible to monitor
multiple cgroup in parallel. There is one cgroup per event. The cgroups to
monitor are passed via a new -G option followed by a comma separated list of
cgroup names.
The cgroup filesystem has to be mounted. Given a cgroup name, the perf tool
finds the corresponding directory in the cgroup filesystem and opens it. It
then passes that file descriptor to the kernel.
Example:
$ perf stat -B -a -e cycles:u,cycles:u,cycles:u -G test1,,test2 -- sleep 1
Performance counter stats for 'sleep 1':
2,368,667,414 cycles test1
2,369,661,459 cycles
<not counted> cycles test2
1.001856890 seconds time elapsed
Signed-off-by: Stephane Eranian <eranian@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <4d590290.825bdf0a.7d0a.4890@mx.google.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2011-02-14 17:20:01 +08:00
LIB_H += util/cgroup.h
2009-04-27 14:02:14 +08:00
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/abspath.o
LIB_OBJS += $( OUTPUT) util/alias.o
2011-02-04 19:45:46 +08:00
LIB_OBJS += $( OUTPUT) util/annotate.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/build-id.o
LIB_OBJS += $( OUTPUT) util/config.o
LIB_OBJS += $( OUTPUT) util/ctype.o
LIB_OBJS += $( OUTPUT) util/debugfs.o
LIB_OBJS += $( OUTPUT) util/environment.o
LIB_OBJS += $( OUTPUT) util/event.o
2011-01-12 06:56:53 +08:00
LIB_OBJS += $( OUTPUT) util/evlist.o
2011-01-04 02:39:04 +08:00
LIB_OBJS += $( OUTPUT) util/evsel.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/exec_cmd.o
LIB_OBJS += $( OUTPUT) util/help.o
LIB_OBJS += $( OUTPUT) util/levenshtein.o
LIB_OBJS += $( OUTPUT) util/parse-options.o
LIB_OBJS += $( OUTPUT) util/parse-events.o
LIB_OBJS += $( OUTPUT) util/path.o
LIB_OBJS += $( OUTPUT) util/rbtree.o
LIB_OBJS += $( OUTPUT) util/bitmap.o
LIB_OBJS += $( OUTPUT) util/hweight.o
LIB_OBJS += $( OUTPUT) util/run-command.o
LIB_OBJS += $( OUTPUT) util/quote.o
LIB_OBJS += $( OUTPUT) util/strbuf.o
LIB_OBJS += $( OUTPUT) util/string.o
LIB_OBJS += $( OUTPUT) util/strlist.o
2011-01-20 22:15:30 +08:00
LIB_OBJS += $( OUTPUT) util/strfilter.o
2011-02-01 00:50:39 +08:00
LIB_OBJS += $( OUTPUT) util/top.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/usage.o
LIB_OBJS += $( OUTPUT) util/wrapper.o
LIB_OBJS += $( OUTPUT) util/sigchain.o
LIB_OBJS += $( OUTPUT) util/symbol.o
LIB_OBJS += $( OUTPUT) util/color.o
LIB_OBJS += $( OUTPUT) util/pager.o
LIB_OBJS += $( OUTPUT) util/header.o
LIB_OBJS += $( OUTPUT) util/callchain.o
LIB_OBJS += $( OUTPUT) util/values.o
LIB_OBJS += $( OUTPUT) util/debug.o
LIB_OBJS += $( OUTPUT) util/map.o
2010-05-15 07:05:21 +08:00
LIB_OBJS += $( OUTPUT) util/pstack.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/session.o
LIB_OBJS += $( OUTPUT) util/thread.o
2011-01-19 01:15:24 +08:00
LIB_OBJS += $( OUTPUT) util/thread_map.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/trace-event-parse.o
LIB_OBJS += $( OUTPUT) util/trace-event-read.o
LIB_OBJS += $( OUTPUT) util/trace-event-info.o
LIB_OBJS += $( OUTPUT) util/trace-event-scripting.o
LIB_OBJS += $( OUTPUT) util/svghelper.o
LIB_OBJS += $( OUTPUT) util/sort.o
LIB_OBJS += $( OUTPUT) util/hist.o
LIB_OBJS += $( OUTPUT) util/probe-event.o
LIB_OBJS += $( OUTPUT) util/util.o
2011-01-04 02:39:04 +08:00
LIB_OBJS += $( OUTPUT) util/xyarray.o
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/cpumap.o
perf tool: Add cgroup support
This patch adds the ability to filter monitoring based on container groups
(cgroups) for both perf stat and perf record. It is possible to monitor
multiple cgroup in parallel. There is one cgroup per event. The cgroups to
monitor are passed via a new -G option followed by a comma separated list of
cgroup names.
The cgroup filesystem has to be mounted. Given a cgroup name, the perf tool
finds the corresponding directory in the cgroup filesystem and opens it. It
then passes that file descriptor to the kernel.
Example:
$ perf stat -B -a -e cycles:u,cycles:u,cycles:u -G test1,,test2 -- sleep 1
Performance counter stats for 'sleep 1':
2,368,667,414 cycles test1
2,369,661,459 cycles
<not counted> cycles test2
1.001856890 seconds time elapsed
Signed-off-by: Stephane Eranian <eranian@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <4d590290.825bdf0a.7d0a.4890@mx.google.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2011-02-14 17:20:01 +08:00
LIB_OBJS += $( OUTPUT) util/cgroup.o
2010-03-28 01:30:45 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-annotate.o
BUILTIN_OBJS += $( OUTPUT) builtin-bench.o
2009-11-05 08:31:37 +08:00
# Benchmark modules
2010-03-28 01:30:45 +08:00
BUILTIN_OBJS += $( OUTPUT) bench/sched-messaging.o
BUILTIN_OBJS += $( OUTPUT) bench/sched-pipe.o
2010-11-25 15:04:53 +08:00
i f e q ( $( RAW_ARCH ) , x 8 6 _ 6 4 )
BUILTIN_OBJS += $( OUTPUT) bench/mem-memcpy-x86-64-asm.o
e n d i f
2010-03-28 01:30:45 +08:00
BUILTIN_OBJS += $( OUTPUT) bench/mem-memcpy.o
BUILTIN_OBJS += $( OUTPUT) builtin-diff.o
2011-03-15 22:04:13 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-evlist.o
2010-03-28 01:30:45 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-help.o
BUILTIN_OBJS += $( OUTPUT) builtin-sched.o
BUILTIN_OBJS += $( OUTPUT) builtin-buildid-list.o
BUILTIN_OBJS += $( OUTPUT) builtin-buildid-cache.o
BUILTIN_OBJS += $( OUTPUT) builtin-list.o
BUILTIN_OBJS += $( OUTPUT) builtin-record.o
BUILTIN_OBJS += $( OUTPUT) builtin-report.o
BUILTIN_OBJS += $( OUTPUT) builtin-stat.o
BUILTIN_OBJS += $( OUTPUT) builtin-timechart.o
BUILTIN_OBJS += $( OUTPUT) builtin-top.o
2010-11-17 01:45:39 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-script.o
2010-03-28 01:30:45 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-probe.o
BUILTIN_OBJS += $( OUTPUT) builtin-kmem.o
BUILTIN_OBJS += $( OUTPUT) builtin-lock.o
2010-04-19 13:32:50 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-kvm.o
perf test: Initial regression testing command
First an example with the first internal test:
[acme@doppio linux-2.6-tip]$ perf test
1: vmlinux symtab matches kallsyms: Ok
So it run just one test, that is "vmlinux symtab matches kallsyms", and it was
successful.
If we run it in verbose mode, we'll see details about errors and extra warnings
for non-fatal problems:
[acme@doppio linux-2.6-tip]$ perf test -v
1: vmlinux symtab matches kallsyms:
--- start ---
Looking at the vmlinux_path (5 entries long)
No build_id in vmlinux, ignoring it
No build_id in /boot/vmlinux, ignoring it
No build_id in /boot/vmlinux-2.6.34-rc4-tip+, ignoring it
Using /lib/modules/2.6.34-rc4-tip+/build/vmlinux for symbols
Maps only in vmlinux:
ffffffff81cb81b1-ffffffff81e1149b 0 [kernel].init.text
ffffffff81e1149c-ffffffff9fffffff 0 [kernel].exit.text
ffffffffff600000-ffffffffff6000ff 0 [kernel].vsyscall_0
ffffffffff600100-ffffffffff6003ff 0 [kernel].vsyscall_fn
ffffffffff600400-ffffffffff6007ff 0 [kernel].vsyscall_1
ffffffffff600800-ffffffffffffffff 0 [kernel].vsyscall_2
Maps in vmlinux with a different name in kallsyms:
ffffffffff600000-ffffffffff6000ff 0 [kernel].vsyscall_0 in kallsyms as [kernel].0
ffffffffff600100-ffffffffff6003ff 0 [kernel].vsyscall_fn in kallsyms as:
*ffffffffff600100-ffffffffff60012f 0 [kernel].2
ffffffffff600400-ffffffffff6007ff 0 [kernel].vsyscall_1 in kallsyms as [kernel].6
ffffffffff600800-ffffffffffffffff 0 [kernel].vsyscall_2 in kallsyms as [kernel].8
Maps only in kallsyms:
ffffffffff600130-ffffffffff6003ff 0 [kernel].4
---- end ----
vmlinux symtab matches kallsyms: Ok
[acme@doppio linux-2.6-tip]$
In the above case we only know the name of the non contiguous kernel ranges in
the address space when reading the symbol information from the ELF symtab in
vmlinux.
The /proc/kallsyms file lack this, we only notice they are separate because
there are modules after the kernel and after that more kernel functions, so we
need to have a module rbtree backed by the module .ko path to get symtabs in
the vmlinux case.
The tool uses it to match by address to emit appropriate warning, but don't
considers this fatal.
The .init.text and .exit.text ines, of course, aren't in kallsyms, so I left
these cases just as extra info in verbose mode.
The end of the sections also aren't in kallsyms, so we the symbols layer does
another pass and sets the end addresses as the next map start minus one, which
sometimes pads, causing harmless mismatches.
But at least the symbols match, tested it by copying /proc/kallsyms to
/tmp/kallsyms and doing changes to see if they were detected.
This first test also should serve as a first stab at documenting the
symbol library by providing a self contained example that exercises it
together with comments about what is being done.
More tests to check if actions done on a monitored app, like doing mmaps, etc,
makes the kernel generate the expected events should be added next.
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-04-30 05:58:32 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-test.o
2010-05-01 14:41:20 +08:00
BUILTIN_OBJS += $( OUTPUT) builtin-inject.o
2009-04-20 21:00:56 +08:00
PERFLIBS = $( LIB_FILE)
2009-04-20 19:32:07 +08:00
perf tools: Initial python binding
First clarifying that this kind of binding is not a replacement or an
equivalent to the 'perf script' way of using python with perf.
The 'perf script' way is to process events and look at a given script
for some python function that matches the events to pass each event for
processing.
This is a python module, i.e. everything is driven from the python
script, that merely uses "import perf" or "from perf import".
perf script is focused on tracepoints, this binding is focused on profiling as
an initial target. More work is needed to make available tracepoint specific
variables as event variables accessible via this binding.
There is one example of such usage model, in
tools/perf/python/twatch.py, a tool to watch "cycles" events together
with task (fork, exit) and comm perf events.
For now, due to me not being able to grok how python distutils cope with
building C extensions outside the sources dir the install target just
builds it, I'm using it as:
[root@emilia linux]# export PYTHONPATH=~acme/git/build/perf/lib.linux-x86_64-2.6/
[root@emilia linux]# tools/perf/python/twatch.py
cpu: 4, pid: 30126, tid: 30126 { type: mmap, pid: 30126, tid: 30126, start: 0x4, length: 0x82e9ca03, offset: 0, filename: }
cpu: 6, pid: 47, tid: 47 { type: mmap, pid: 47, tid: 47, start: 0x6, length: 0xbef87c36, offset: 0, filename: }
cpu: 1, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0x1, length: 0x775d1904, offset: 0, filename: }
cpu: 7, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0x7, length: 0xc750aeb6, offset: 0, filename: }
cpu: 5, pid: 2255, tid: 2255 { type: mmap, pid: 2255, tid: 2255, start: 0x5, length: 0x76669635, offset: 0, filename: }
cpu: 0, pid: 0, tid: 0 { type: mmap, pid: 0, tid: 0, start: 0, length: 0x6422ef6b, offset: 0, filename: }
cpu: 2, pid: 2255, tid: 2255 { type: mmap, pid: 2255, tid: 2255, start: 0x2, length: 0xe078757a, offset: 0, filename: }
cpu: 1, pid: 5769, tid: 5769 { type: fork, pid: 30127, ppid: 5769, tid: 30127, ptid: 5769, time: 103893991270534}
cpu: 6, pid: 30127, tid: 30127 { type: comm, pid: 30127, tid: 30127, comm: ls }
cpu: 6, pid: 30127, tid: 30127 { type: exit, pid: 30127, ppid: 30127, tid: 30127, ptid: 30127, time: 103893993273024}
The first 8 mmap events in this 8 way machine are a mistery that is still being
investigated.
More of the tools/perf/util/ APIs will be exposed via this python binding as
the need arises. For now the focus is on creating events and processing them,
symbol resolution is an obvious next step, with tracepoint variables as a close
second step.
Cc: Clark Williams <williams@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-01-30 01:44:29 +08:00
# Files needed for the python binding, perf.so
# pyrf is just an internal name needed for all those wrappers.
# This has to be in sync with what is in the 'sources' variable in
# tools/perf/util/setup.py
PYRF_OBJS += $( OUTPUT) util/cpumap.o
PYRF_OBJS += $( OUTPUT) util/ctype.o
PYRF_OBJS += $( OUTPUT) util/evlist.o
PYRF_OBJS += $( OUTPUT) util/evsel.o
PYRF_OBJS += $( OUTPUT) util/python.o
PYRF_OBJS += $( OUTPUT) util/thread_map.o
PYRF_OBJS += $( OUTPUT) util/util.o
PYRF_OBJS += $( OUTPUT) util/xyarray.o
2009-04-20 19:32:07 +08:00
#
# Platform specific tweaks
#
# We choose to avoid "if .. else if .. else .. endif endif"
# because maintaining the nesting to match is a pain. If
# we had "elif" things would have been much nicer...
- i n c l u d e c o n f i g . m a k . a u t o g e n
- i n c l u d e c o n f i g . m a k
2010-04-20 14:58:32 +08:00
i f n d e f N O _ D W A R F
2010-11-17 06:16:33 +08:00
FLAGS_DWARF = $( ALL_CFLAGS) -ldw -lelf $( ALL_LDFLAGS) $( EXTLIBS)
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
i f n e q ( $( call try -cc ,$ ( SOURCE_DWARF ) ,$ ( FLAGS_DWARF ) ) , y )
2010-05-11 12:59:53 +08:00
msg := $( warning No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev) ;
2010-04-20 14:58:32 +08:00
NO_DWARF := 1
e n d i f # Dwarf support
e n d i f # NO_DWARF
- i n c l u d e a r c h / $( ARCH ) / M a k e f i l e
2010-03-28 01:30:45 +08:00
i f n e q ( $( OUTPUT ) , )
BASIC_CFLAGS += -I$( OUTPUT)
e n d i f
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
FLAGS_LIBELF = $( ALL_CFLAGS) $( ALL_LDFLAGS) $( EXTLIBS)
i f n e q ( $( call try -cc ,$ ( SOURCE_LIBELF ) ,$ ( FLAGS_LIBELF ) ) , y )
FLAGS_GLIBC = $( ALL_CFLAGS) $( ALL_LDFLAGS)
ifneq ( $( call try-cc,$( SOURCE_GLIBC) ,$( FLAGS_GLIBC) ) ,y)
msg := $( error No gnu/libc-version.h found, please install glibc-dev[ el] /glibc-static) ;
else
msg := $( error No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel) ;
endif
2009-10-19 10:20:24 +08:00
e n d i f
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
i f n e q ( $( call try -cc ,$ ( SOURCE_ELF_MMAP ) ,$ ( FLAGS_COMMON ) ) , y )
BASIC_CFLAGS += -DLIBELF_NO_MMAP
2009-08-05 20:05:16 +08:00
e n d i f
2010-03-23 00:10:27 +08:00
i f n d e f N O _ D W A R F
2010-04-20 14:58:32 +08:00
i f e q ( $( origin PERF_HAVE_DWARF_REGS ) , u n d e f i n e d )
msg := $( warning DWARF register mappings have not been defined for architecture $( ARCH) , DWARF support disabled) ;
e l s e
2010-11-17 06:16:33 +08:00
BASIC_CFLAGS += -DDWARF_SUPPORT
2010-02-25 21:35:42 +08:00
EXTLIBS += -lelf -ldw
2010-03-28 01:30:45 +08:00
LIB_OBJS += $( OUTPUT) util/probe-finder.o
2011-06-27 15:27:27 +08:00
LIB_OBJS += $( OUTPUT) util/dwarf-aux.o
2010-04-20 14:58:32 +08:00
e n d i f # PERF_HAVE_DWARF_REGS
e n d i f # NO_DWARF
2009-10-09 05:17:38 +08:00
2010-05-18 05:18:11 +08:00
i f d e f N O _ N E W T
BASIC_CFLAGS += -DNO_NEWT_SUPPORT
e l s e
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
FLAGS_NEWT = $( ALL_CFLAGS) $( ALL_LDFLAGS) $( EXTLIBS) -lnewt
ifneq ( $( call try-cc,$( SOURCE_NEWT) ,$( FLAGS_NEWT) ) ,y)
msg := $( warning newt not found, disables TUI support. Please install newt-devel or libnewt-dev) ;
BASIC_CFLAGS += -DNO_NEWT_SUPPORT
else
# Fedora has /usr/include/slang/slang.h, but ubuntu /usr/include/slang.h
BASIC_CFLAGS += -I/usr/include/slang
EXTLIBS += -lnewt -lslang
2010-08-11 02:58:50 +08:00
LIB_OBJS += $( OUTPUT) util/ui/setup.o
2010-08-07 04:35:02 +08:00
LIB_OBJS += $( OUTPUT) util/ui/browser.o
2010-08-11 01:54:09 +08:00
LIB_OBJS += $( OUTPUT) util/ui/browsers/annotate.o
2010-08-11 02:49:07 +08:00
LIB_OBJS += $( OUTPUT) util/ui/browsers/hists.o
2010-08-11 02:37:34 +08:00
LIB_OBJS += $( OUTPUT) util/ui/browsers/map.o
2010-08-09 06:48:31 +08:00
LIB_OBJS += $( OUTPUT) util/ui/helpline.o
2010-08-09 06:56:47 +08:00
LIB_OBJS += $( OUTPUT) util/ui/progress.o
2010-08-11 02:58:50 +08:00
LIB_OBJS += $( OUTPUT) util/ui/util.o
2010-08-07 04:35:02 +08:00
LIB_H += util/ui/browser.h
2010-08-11 02:37:34 +08:00
LIB_H += util/ui/browsers/map.h
2010-08-09 06:48:31 +08:00
LIB_H += util/ui/helpline.h
2011-10-21 02:59:15 +08:00
LIB_H += util/ui/keysyms.h
2010-08-11 01:54:09 +08:00
LIB_H += util/ui/libslang.h
2010-08-09 06:56:47 +08:00
LIB_H += util/ui/progress.h
2010-08-11 02:58:50 +08:00
LIB_H += util/ui/util.h
2011-02-09 21:38:43 +08:00
LIB_H += util/ui/ui.h
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
endif
2009-12-11 17:21:00 +08:00
e n d i f
2009-11-25 15:15:48 +08:00
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
i f d e f N O _ L I B P E R L
2009-11-25 15:15:48 +08:00
BASIC_CFLAGS += -DNO_LIBPERL
e l s e
2010-08-24 13:23:50 +08:00
PERL_EMBED_LDOPTS = $( shell perl -MExtUtils::Embed -e ldopts 2>/dev/null)
PERL_EMBED_LDFLAGS = $( call strip-libs,$( PERL_EMBED_LDOPTS) )
PERL_EMBED_LIBADD = $( call grep-libs,$( PERL_EMBED_LDOPTS) )
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
PERL_EMBED_CCOPTS = ` perl -MExtUtils::Embed -e ccopts 2>/dev/null`
2010-06-18 12:40:06 +08:00
FLAGS_PERL_EMBED = $( PERL_EMBED_CCOPTS) $( PERL_EMBED_LDOPTS)
2009-11-25 15:15:48 +08:00
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
ifneq ( $( call try-cc,$( SOURCE_PERL_EMBED) ,$( FLAGS_PERL_EMBED) ) ,y)
BASIC_CFLAGS += -DNO_LIBPERL
else
2010-08-24 13:23:50 +08:00
ALL_LDFLAGS += $( PERL_EMBED_LDFLAGS)
EXTLIBS += $( PERL_EMBED_LIBADD)
perf tools: Reorganize the Makefile feature tests
Moving the tests to a separate file, feature-tests.mak and using a try-cc
function similar to the try-run in Kbuild.
This also makes the output more quiet as we can stop using the INTERMEDIATE
target to remove the .perf.dev.null file needed for some gcc versions where
/dev/null can't be used as the output file name.
As the tests get shorter by uninlining the source code used to test for
features, we can more properly use identation.
The feature tests itself can be made more clear and reused, like when trying to
see what is needed to have bfd_demangle.
We also get a bit closer to reusing scripts/Kbuild.include, reducing the
distance from the kernel build system.
Tests performed:
[root@emilia perf]# make -j9 O=/tmp/perf
PERF_VERSION = 0.0.2.PERF
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/builtin-annotate.o
CC /tmp/perf/bench/sched-messaging.o
CC /tmp/perf/builtin-diff.o
<SNIP>
CC /tmp/perf/scripts/python/Perf-Trace-Util/Context.o
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-help.o
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
If we uninstall, for instance newt-devel we get:
[root@emilia perf]# rpm -e newt-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then binutils-devel:
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:564: newt not found, disables TUI support. Please install newt-devel or libnewt-dev
Makefile:632: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling
* new build flags or prefix
GEN perf-archive
CC /tmp/perf/perf.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
[root@emilia perf]#
And then strictly required devel packages:
[root@emilia perf]# rpm -e elfutils-libelf-devel elfutils-devel
[root@emilia perf]# make -j9 O=/tmp/perf
Makefile:509: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev
Makefile:542: *** No libelf.h/libelf found, please install libelf-dev/elfutils-libelf-devel. Stop.
[root@emilia perf]#
After installing everything back on:
[root@emilia perf]# yum install elfutils-devel binutils-devel newt-devel
<SNIP>
Installed:
binutils-devel.x86_64 0:2.20.51.0.2-5.11.el6
elfutils-devel.x86_64 0:0.147-1.el6
elfutils-libelf-devel.x86_64 0:0.147-1.el6
newt-devel.x86_64 0:0.52.11-1.el6
Complete!
[root@emilia perf]# make -j9
PERF_VERSION = 0.0.2.PERF
GEN common-cmds.h
* new build flags or prefix
GEN perf-archive
CC builtin-annotate.o
<SNIP>
AR libperf.a
LINK perf
[root@emilia perf]# make -j9
[root@emilia perf]#
Thanks to Sam for pointing me to try-run.
Cc: David S. Miller <davem@davemloft.net>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Michal Marek <mmarek@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-06-10 03:57:39 +08:00
LIB_OBJS += $( OUTPUT) util/scripting-engines/trace-event-perl.o
LIB_OBJS += $( OUTPUT) scripts/perl/Perf-Trace-Util/Context.o
endif
2010-01-27 16:27:57 +08:00
e n d i f
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
disable-python = $( eval $( disable-python_code) )
d e f i n e d i s a b l e - p y t h o n _ c o d e
BASIC_CFLAGS += -DNO_LIBPYTHON
$( if $( 1) ,$( warning No $( 1) was found) )
$( warning Python support won' t be built)
e n d e f
override PYTHON : = \
$( call get-executable-or-default,PYTHON,python)
i f n d e f P Y T H O N
$( call disable-python,python interpreter)
python-clean :=
2010-01-27 16:27:57 +08:00
e l s e
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
PYTHON_WORD := $( call shell-wordify,$( PYTHON) )
2011-07-22 19:33:07 +08:00
# python extension build directories
PYTHON_EXTBUILD := $( OUTPUT) python_ext_build/
PYTHON_EXTBUILD_LIB := $( PYTHON_EXTBUILD) lib/
PYTHON_EXTBUILD_TMP := $( PYTHON_EXTBUILD) tmp/
export PYTHON_EXTBUILD_LIB PYTHON_EXTBUILD_TMP
python-clean := rm -rf $( PYTHON_EXTBUILD) $( OUTPUT) python/perf.so
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
ifdef NO_LIBPYTHON
$( call disable-python)
else
override PYTHON_CONFIG := \
$( call get-executable-or-default,PYTHON_CONFIG,$( PYTHON) -config)
ifndef PYTHON_CONFIG
$( call disable-python,python-config tool)
else
PYTHON_CONFIG_SQ := $( call shell-sq,$( PYTHON_CONFIG) )
PYTHON_EMBED_LDOPTS := $( shell $( PYTHON_CONFIG_SQ) --ldflags 2>/dev/null)
PYTHON_EMBED_LDFLAGS := $( call strip-libs,$( PYTHON_EMBED_LDOPTS) )
PYTHON_EMBED_LIBADD := $( call grep-libs,$( PYTHON_EMBED_LDOPTS) )
PYTHON_EMBED_CCOPTS := $( shell $( PYTHON_CONFIG_SQ) --cflags 2>/dev/null)
FLAGS_PYTHON_EMBED := $( PYTHON_EMBED_CCOPTS) $( PYTHON_EMBED_LDOPTS)
ifneq ( $( call try-cc,$( SOURCE_PYTHON_EMBED) ,$( FLAGS_PYTHON_EMBED) ) ,y)
$( call disable-python,Python.h ( for Python 2.x) )
else
ifneq ( $( call try-cc,$( SOURCE_PYTHON_VERSION) ,$( FLAGS_PYTHON_EMBED) ) ,y)
$( warning Python 3 is not yet supported; please set )
$( warning PYTHON and/or PYTHON_CONFIG appropriately.)
$( warning If you also have Python 2 installed, then )
$( warning try something like:)
$( warning $( and ,) )
$( warning $( and ,) make PYTHON = python2)
$( warning $( and ,) )
$( warning Otherwise, disable Python support entirely:)
$( warning $( and ,) )
$( warning $( and ,) make NO_LIBPYTHON = 1)
$( warning $( and ,) )
$( error $( and ,) )
else
ALL_LDFLAGS += $( PYTHON_EMBED_LDFLAGS)
EXTLIBS += $( PYTHON_EMBED_LIBADD)
LIB_OBJS += $( OUTPUT) util/scripting-engines/trace-event-python.o
LIB_OBJS += $( OUTPUT) scripts/python/Perf-Trace-Util/Context.o
LANG_BINDINGS += $( OUTPUT) python/perf.so
endif
endif
endif
endif
2010-01-27 16:27:57 +08:00
e n d i f
2009-08-05 20:05:16 +08:00
i f d e f N O _ D E M A N G L E
BASIC_CFLAGS += -DNO_DEMANGLE
e l s e
2010-07-01 21:19:26 +08:00
ifdef HAVE_CPLUS_DEMANGLE
EXTLIBS += -liberty
BASIC_CFLAGS += -DHAVE_CPLUS_DEMANGLE
else
FLAGS_BFD = $( ALL_CFLAGS) $( ALL_LDFLAGS) $( EXTLIBS) -lbfd
has_bfd := $( call try-cc,$( SOURCE_BFD) ,$( FLAGS_BFD) )
ifeq ( $( has_bfd) ,y)
EXTLIBS += -lbfd
2009-08-12 03:22:11 +08:00
else
2010-07-01 21:19:26 +08:00
FLAGS_BFD_IBERTY = $( FLAGS_BFD) -liberty
has_bfd_iberty := $( call try-cc,$( SOURCE_BFD) ,$( FLAGS_BFD_IBERTY) )
ifeq ( $( has_bfd_iberty) ,y)
EXTLIBS += -lbfd -liberty
2009-08-12 03:22:11 +08:00
else
2010-07-01 21:19:26 +08:00
FLAGS_BFD_IBERTY_Z = $( FLAGS_BFD_IBERTY) -lz
has_bfd_iberty_z := $( call try-cc,$( SOURCE_BFD) ,$( FLAGS_BFD_IBERTY_Z) )
ifeq ( $( has_bfd_iberty_z) ,y)
EXTLIBS += -lbfd -liberty -lz
2009-08-12 03:22:11 +08:00
else
2010-07-01 21:19:26 +08:00
FLAGS_CPLUS_DEMANGLE = $( ALL_CFLAGS) $( ALL_LDFLAGS) $( EXTLIBS) -liberty
has_cplus_demangle := $( call try-cc,$( SOURCE_CPLUS_DEMANGLE) ,$( FLAGS_CPLUS_DEMANGLE) )
ifeq ( $( has_cplus_demangle) ,y)
EXTLIBS += -liberty
BASIC_CFLAGS += -DHAVE_CPLUS_DEMANGLE
else
msg := $( warning No bfd.h/libbfd found, install binutils-dev[ el] /zlib-static to gain symbol demangling)
BASIC_CFLAGS += -DNO_DEMANGLE
endif
2009-08-12 03:22:11 +08:00
endif
endif
endif
2009-08-05 20:05:16 +08:00
endif
e n d i f
2010-08-21 08:38:20 +08:00
i f d e f N O _ S T R L C P Y
BASIC_CFLAGS += -DNO_STRLCPY
e l s e
ifneq ( $( call try-cc,$( SOURCE_STRLCPY) ,) ,y)
BASIC_CFLAGS += -DNO_STRLCPY
endif
e n d i f
2009-04-20 19:32:07 +08:00
i f n e q ( $( findstring $ ( MAKEFLAGS ) ,s ) , s )
i f n d e f V
QUIET_CC = @echo ' ' CC $@ ;
QUIET_AR = @echo ' ' AR $@ ;
QUIET_LINK = @echo ' ' LINK $@ ;
2010-08-17 23:22:08 +08:00
QUIET_MKDIR = @echo ' ' MKDIR $@ ;
2009-04-20 19:32:07 +08:00
QUIET_GEN = @echo ' ' GEN $@ ;
e n d i f
e n d i f
i f d e f A S C I I D O C 8
export ASCIIDOC8
e n d i f
# Shell quote (do not use $(call) to accommodate ancient setups);
2009-04-20 21:00:56 +08:00
ETC_PERFCONFIG_SQ = $( subst ',' \' ' ,$( ETC_PERFCONFIG) )
2009-04-20 19:32:07 +08:00
DESTDIR_SQ = $( subst ',' \' ' ,$( DESTDIR) )
bindir_SQ = $( subst ',' \' ' ,$( bindir) )
bindir_relative_SQ = $( subst ',' \' ' ,$( bindir_relative) )
mandir_SQ = $( subst ',' \' ' ,$( mandir) )
infodir_SQ = $( subst ',' \' ' ,$( infodir) )
2009-04-20 21:00:56 +08:00
perfexecdir_SQ = $( subst ',' \' ' ,$( perfexecdir) )
2009-04-20 19:32:07 +08:00
template_dir_SQ = $( subst ',' \' ' ,$( template_dir) )
htmldir_SQ = $( subst ',' \' ' ,$( htmldir) )
prefix_SQ = $( subst ',' \' ' ,$( prefix) )
SHELL_PATH_SQ = $( subst ',' \' ' ,$( SHELL_PATH) )
2011-06-16 05:03:38 +08:00
LIBS = -Wl,--whole-archive $( PERFLIBS) -Wl,--no-whole-archive -Wl,--start-group $( EXTLIBS) -Wl,--end-group
2009-04-20 19:32:07 +08:00
ALL_CFLAGS += $( BASIC_CFLAGS)
2010-11-25 15:04:53 +08:00
ALL_CFLAGS += $( ARCH_CFLAGS)
2009-04-20 19:32:07 +08:00
ALL_LDFLAGS += $( BASIC_LDFLAGS)
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
export INSTALL SHELL_PATH
2009-04-20 19:32:07 +08:00
### Build rules
SHELL = $( SHELL_PATH)
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
all : shell_compatibility_test $( ALL_PROGRAMS ) $( LANG_BINDINGS ) $( OTHER_PROGRAMS )
2009-04-20 19:32:07 +08:00
please_set_SHELL_PATH_to_a_more_modern_shell :
@$$ ( :)
shell_compatibility_test : please_set_SHELL_PATH_to_a_more_modern_shell
2011-02-03 01:57:41 +08:00
strip : $( PROGRAMS ) $( OUTPUT ) perf
$( STRIP) $( STRIP_OPTS) $( PROGRAMS) $( OUTPUT) perf
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)perf.o : perf .c $( OUTPUT ) common -cmds .h $( OUTPUT ) PERF -CFLAGS
2009-04-20 21:00:56 +08:00
$( QUIET_CC) $( CC) -DPERF_VERSION= '"$(PERF_VERSION)"' \
'-DPERF_HTML_PATH="$(htmldir_SQ)"' \
2010-03-28 01:30:45 +08:00
$( ALL_CFLAGS) -c $( filter %.c,$^) -o $@
2009-04-20 19:32:07 +08:00
2011-02-03 01:57:41 +08:00
$(OUTPUT)perf : $( OUTPUT ) perf .o $( BUILTIN_OBJS ) $( PERFLIBS )
2010-08-24 13:23:50 +08:00
$( QUIET_LINK) $( CC) $( ALL_CFLAGS) $( ALL_LDFLAGS) $( OUTPUT) perf.o \
$( BUILTIN_OBJS) $( LIBS) -o $@
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)builtin-help.o : builtin -help .c $( OUTPUT ) common -cmds .h $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) \
2009-04-20 21:00:56 +08:00
'-DPERF_HTML_PATH="$(htmldir_SQ)"' \
'-DPERF_MAN_PATH="$(mandir_SQ)"' \
2009-09-12 13:53:05 +08:00
'-DPERF_INFO_PATH="$(infodir_SQ)"' $<
2010-03-28 01:30:45 +08:00
$(OUTPUT)builtin-timechart.o : builtin -timechart .c $( OUTPUT ) common -cmds .h $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) \
2009-09-12 13:53:05 +08:00
'-DPERF_HTML_PATH="$(htmldir_SQ)"' \
'-DPERF_MAN_PATH="$(mandir_SQ)"' \
2009-04-20 21:00:56 +08:00
'-DPERF_INFO_PATH="$(infodir_SQ)"' $<
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)common-cmds.h : util /generate -cmdlist .sh command -list .txt
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)common-cmds.h : $( wildcard Documentation /perf -*.txt )
2009-09-26 03:01:41 +08:00
$( QUIET_GEN) . util/generate-cmdlist.sh > $@ + && mv $@ + $@
2009-04-20 19:32:07 +08:00
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
$(SCRIPTS) : % : %.sh
$( QUIET_GEN) $( INSTALL) '$@.sh' '$(OUTPUT)$@'
2009-04-20 19:32:07 +08:00
2009-04-20 21:00:56 +08:00
# These can record PERF_VERSION
2010-03-28 01:30:45 +08:00
$( OUTPUT ) p e r f . o p e r f . s p e c \
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
$( SCRIPTS) \
2010-03-28 01:30:45 +08:00
: $( OUTPUT) PERF-VERSION-FILE
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)%.o : %.c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $<
$(OUTPUT)%.s : %.c $( OUTPUT ) PERF -CFLAGS
2009-04-20 19:32:07 +08:00
$( QUIET_CC) $( CC) -S $( ALL_CFLAGS) $<
2010-03-28 01:30:45 +08:00
$(OUTPUT)%.o : %.S
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $<
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)util/exec_cmd.o : util /exec_cmd .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) \
2009-04-20 21:00:56 +08:00
'-DPERF_EXEC_PATH="$(perfexecdir_SQ)"' \
2009-04-20 19:32:07 +08:00
'-DBINDIR="$(bindir_relative_SQ)"' \
'-DPREFIX="$(prefix_SQ)"' \
$<
2010-03-28 01:30:45 +08:00
$(OUTPUT)util/config.o : util /config .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DETC_PERFCONFIG= '"$(ETC_PERFCONFIG_SQ)"' $<
2009-04-20 19:32:07 +08:00
2010-08-07 04:35:02 +08:00
$(OUTPUT)util/ui/browser.o : util /ui /browser .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DENABLE_SLFUTURE_CONST $<
2010-08-11 01:54:09 +08:00
$(OUTPUT)util/ui/browsers/annotate.o : util /ui /browsers /annotate .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DENABLE_SLFUTURE_CONST $<
2010-08-11 02:49:07 +08:00
$(OUTPUT)util/ui/browsers/hists.o : util /ui /browsers /hists .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DENABLE_SLFUTURE_CONST $<
2010-08-11 02:37:34 +08:00
$(OUTPUT)util/ui/browsers/map.o : util /ui /browsers /map .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DENABLE_SLFUTURE_CONST $<
2010-03-28 01:30:45 +08:00
$(OUTPUT)util/rbtree.o : ../../lib /rbtree .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) -DETC_PERFCONFIG= '"$(ETC_PERFCONFIG_SQ)"' $<
2009-07-01 23:28:37 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)util/scripting-engines/trace-event-perl.o : util /scripting -engines /trace -event -perl .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $( PERL_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes -Wno-unused-parameter -Wno-shadow $<
2009-11-25 15:15:48 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)scripts/perl/Perf-Trace-Util/Context.o : scripts /perl /Perf -Trace -Util /Context .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $( PERL_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes -Wno-unused-parameter -Wno-nested-externs $<
2009-11-25 15:15:50 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)util/scripting-engines/trace-event-python.o : util /scripting -engines /trace -event -python .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $( PYTHON_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes -Wno-unused-parameter -Wno-shadow $<
2010-01-27 16:27:57 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)scripts/python/Perf-Trace-Util/Context.o : scripts /python /Perf -Trace -Util /Context .c $( OUTPUT ) PERF -CFLAGS
$( QUIET_CC) $( CC) -o $@ -c $( ALL_CFLAGS) $( PYTHON_EMBED_CCOPTS) -Wno-redundant-decls -Wno-strict-prototypes -Wno-unused-parameter -Wno-nested-externs $<
2010-01-27 16:27:57 +08:00
2011-02-03 01:57:41 +08:00
$(OUTPUT)perf-% : %.o $( PERFLIBS )
2009-04-20 19:32:07 +08:00
$( QUIET_LINK) $( CC) $( ALL_CFLAGS) -o $@ $( ALL_LDFLAGS) $( filter %.o,$^) $( LIBS)
$(LIB_OBJS) $(BUILTIN_OBJS) : $( LIB_H )
2011-02-03 01:57:41 +08:00
$(patsubst perf-%,%.o,$(PROGRAMS)) : $( LIB_H ) $( wildcard */*.h )
2009-04-20 19:32:07 +08:00
2010-08-17 23:22:08 +08:00
# we compile into subdirectories. if the target directory is not the source directory, they might not exists. So
# we depend the various files onto their directories.
DIRECTORY_DEPS = $( LIB_OBJS) $( BUILTIN_OBJS) $( OUTPUT) PERF-VERSION-FILE $( OUTPUT) common-cmds.h
2010-09-27 01:17:42 +08:00
$(DIRECTORY_DEPS) : | $( sort $ ( dir $ ( DIRECTORY_DEPS ) ) )
2010-08-17 23:22:08 +08:00
# In the second step, we make a rule to actually create these directories
$(sort $(dir $(DIRECTORY_DEPS))) :
$( QUIET_MKDIR) $( MKDIR) -p $@ 2>/dev/null
2009-04-20 19:32:07 +08:00
$(LIB_FILE) : $( LIB_OBJS )
$( QUIET_AR) $( RM) $@ && $( AR) rcs $@ $( LIB_OBJS)
2011-02-10 09:11:00 +08:00
help :
@echo 'Perf make targets:'
@echo ' doc - make *all* documentation (see below)'
@echo ' man - make manpage documentation (access with man <foo>)'
@echo ' html - make html documentation'
@echo ' info - make GNU info documentation (access with info <foo>)'
@echo ' pdf - make pdf documentation'
@echo ' TAGS - use etags to make tag information for source browsing'
@echo ' tags - use ctags to make tag information for source browsing'
@echo ' cscope - use cscope to make interactive browsing database'
@echo ''
@echo 'Perf install targets:'
@echo ' NOTE: documentation build requires asciidoc, xmlto packages to be installed'
@echo ' HINT: use "make prefix=<path> <install target>" to install to a particular'
@echo ' path like make prefix=/usr/local install install-doc'
@echo ' install - install compiled binaries'
@echo ' install-doc - install *all* documentation'
@echo ' install-man - install manpage documentation'
@echo ' install-html - install html documentation'
@echo ' install-info - install GNU info documentation'
@echo ' install-pdf - install pdf documentation'
@echo ''
@echo ' quick-install-doc - alias for quick-install-man'
@echo ' quick-install-man - install the documentation quickly'
@echo ' quick-install-html - install the html documentation quickly'
@echo ''
@echo 'Perf maintainer targets:'
@echo ' distclean - alias to clean'
@echo ' clean - clean all binary objects and build output'
2009-05-30 18:38:51 +08:00
doc :
$( MAKE) -C Documentation all
man :
$( MAKE) -C Documentation man
html :
$( MAKE) -C Documentation html
info :
$( MAKE) -C Documentation info
pdf :
$( MAKE) -C Documentation pdf
2009-04-20 19:32:07 +08:00
TAGS :
$( RM) TAGS
$( FIND) . -name '*.[hcS]' -print | xargs etags -a
tags :
$( RM) tags
$( FIND) . -name '*.[hcS]' -print | xargs ctags -a
cscope :
$( RM) cscope*
$( FIND) . -name '*.[hcS]' -print | xargs cscope -b
### Detect prefix changes
TRACK_CFLAGS = $( subst ',' \' ' ,$( ALL_CFLAGS) ) :\
2009-04-20 21:00:56 +08:00
$( bindir_SQ) :$( perfexecdir_SQ) :$( template_dir_SQ) :$( prefix_SQ)
2009-04-20 19:32:07 +08:00
2010-03-28 01:30:45 +08:00
$(OUTPUT)PERF-CFLAGS : .FORCE -PERF -CFLAGS
2009-04-20 19:32:07 +08:00
@FLAGS= '$(TRACK_CFLAGS)' ; \
2010-03-28 01:30:45 +08:00
if test x" $$ FLAGS " != x" `cat $( OUTPUT) PERF-CFLAGS 2>/dev/null` " ; then \
2009-04-20 19:32:07 +08:00
echo 1>& 2 " * new build flags or prefix" ; \
2010-03-28 01:30:45 +08:00
echo " $$ FLAGS " >$( OUTPUT) PERF-CFLAGS; \
2009-04-20 19:32:07 +08:00
fi
### Testing rules
# GNU make supports exporting all variables by "export" without parameters.
# However, the environment gets quite big, and some programs have problems
# with that.
2010-03-28 01:30:45 +08:00
check : $( OUTPUT ) common -cmds .h
2009-04-20 19:32:07 +08:00
if sparse; \
then \
2009-04-27 14:02:14 +08:00
for i in *.c */*.c; \
2009-04-20 19:32:07 +08:00
do \
sparse $( ALL_CFLAGS) $( SPARSE_FLAGS) $$ i || exit; \
done ; \
else \
exit 1; \
fi
### Installation rules
2009-04-20 21:00:56 +08:00
i f n e q ( $( filter /%,$ ( firstword $ ( perfexecdir ) ) ) , )
perfexec_instdir = $( perfexecdir)
2009-04-20 19:32:07 +08:00
e l s e
2009-04-20 21:00:56 +08:00
perfexec_instdir = $( prefix) /$( perfexecdir)
2009-04-20 19:32:07 +08:00
e n d i f
2009-04-20 21:00:56 +08:00
perfexec_instdir_SQ = $( subst ',' \' ' ,$( perfexec_instdir) )
2009-04-20 19:32:07 +08:00
install : all
$( INSTALL) -d -m 755 '$(DESTDIR_SQ)$(bindir_SQ)'
2011-02-03 01:57:41 +08:00
$( INSTALL) $( OUTPUT) perf '$(DESTDIR_SQ)$(bindir_SQ)'
2009-11-25 15:15:49 +08:00
$( INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/Perf-Trace-Util/lib/Perf/Trace'
$( INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/bin'
2010-03-28 01:30:45 +08:00
$( INSTALL) $( OUTPUT) perf-archive -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)'
2009-11-25 15:15:49 +08:00
$( INSTALL) scripts/perl/Perf-Trace-Util/lib/Perf/Trace/* -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/Perf-Trace-Util/lib/Perf/Trace'
$( INSTALL) scripts/perl/*.pl -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl'
$( INSTALL) scripts/perl/bin/* -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/bin'
2010-01-27 16:27:57 +08:00
$( INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/Perf-Trace-Util/lib/Perf/Trace'
2010-01-27 16:27:58 +08:00
$( INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin'
2010-01-27 16:27:57 +08:00
$( INSTALL) scripts/python/Perf-Trace-Util/lib/Perf/Trace/* -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/Perf-Trace-Util/lib/Perf/Trace'
2010-01-27 16:27:58 +08:00
$( INSTALL) scripts/python/*.py -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python'
$( INSTALL) scripts/python/bin/* -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin'
2010-01-27 16:27:55 +08:00
2011-07-22 19:33:07 +08:00
install-python_ext :
$( PYTHON_WORD) util/setup.py --quiet install --root= '/$(DESTDIR_SQ)'
2009-05-30 18:38:51 +08:00
install-doc :
$( MAKE) -C Documentation install
install-man :
$( MAKE) -C Documentation install-man
install-html :
$( MAKE) -C Documentation install-html
install-info :
$( MAKE) -C Documentation install-info
install-pdf :
$( MAKE) -C Documentation install-pdf
quick-install-doc :
$( MAKE) -C Documentation quick-install
quick-install-man :
$( MAKE) -C Documentation quick-install-man
quick-install-html :
$( MAKE) -C Documentation quick-install-html
2009-04-20 19:32:07 +08:00
### Cleaning rules
2009-03-24 04:29:59 +08:00
clean :
2011-08-07 16:39:31 +08:00
$( RM) $( LIB_OBJS) $( BUILTIN_OBJS) $( LIB_FILE) $( OUTPUT) perf-archive $( OUTPUT) perf.o $( LANG_BINDINGS)
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
$( RM) $( ALL_PROGRAMS) perf
2010-03-28 01:30:45 +08:00
$( RM) *.spec *.pyc *.pyo */*.pyc */*.pyo $( OUTPUT) common-cmds.h TAGS tags cscope*
2009-05-30 18:38:51 +08:00
$( MAKE) -C Documentation/ clean
perf tools: Makefile: Remove various and sundry cruft
This commit squashes several commits that remove:
unnecessary uname calls
`sh -c'
BUILT_INS and QUIET_BUILT_IN
They have no effect, and the `fixup-builtins' and `check-builtins.sh'
scripts don't even exist.
RUNTIME_PREFIX
It's currently never anything but unset, and it's apparently
only meaningful when Microsoft Windows is the operating system
(according to the source for git).
TEST_PROGRAMS
EXTRA_PROGRAMS
unused SHELL_PATH_SQ portions
unused test for V=2
useless exports
Only when `V' is undefined (that is, only when the value of `V'
is empty) is `export V' performed, which just has the effect of
placing the empty-valued variable `V' in the environment.
The only other script to make use of `V' is `Documentation/Makefile',
which only checks whether `V' is undefined (that is, whether the value
of `V' is empty); hence, the `export V' has no effect whatsoever.
Similarly, `export QUIET_GEN' is useless because it will only have
a non-empty value when `V' has an empty-value, and when `V' has
an empty-value, `QUIET_GEN' is always explicitly set in every
script in which it is used.
`DESTDIR' is only ever defined by the user via the environment
or the command line, both of which are automatically exported
to sub-make processes. Furthermore, no non-make sub-scripts
make use of `DESTDIR' as an environment variable.
No other scripts use `perfexec_instdir'.
unused QUIET_SUBDIR{0,1}
TAR and RPMBUILD
PTHREAD_LIBS
Maintainer's dist rules and commands
distclean target
Test suite coverage testing
PRINT_DIR and NO_SUBDIR
`configure' target
NO_CURL
@@PERF_VERSION@@ substitution
Without the sed command, all of the rule's commands can be reduced
to a single line that copies a file and sets the permissions properly
in the process.
`make test' echo line
template_instdir
PERF-BUILD-OPTIONS
double-colon rules
The use of double-colon rules seems misguided or vestigial git.
Essentially hard-coded $(SCRIPTS) expansion
Signed-off-by: Michael Witten <mfwitten@gmail.com>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-02-03 04:22:08 +08:00
$( RM) $( OUTPUT) PERF-VERSION-FILE $( OUTPUT) PERF-CFLAGS
perf tools: Makefile: PYTHON{,_CONFIG} to bandage Python 3 incompatibility
Currently, Python 3 is not supported by perf's code; this
can cause the build to fail for systems that have Python 3
installed as the default python:
python{,-config}
The Correct Solution is to write compatibility code so that
Python 3 works out-of-the-box.
However, users often have an ancillary Python 2 installed:
python2{,-config}
Therefore, a quick fix is to allow the user to specify those
ancillary paths as the python binaries that Makefile should
use, thereby avoiding Python 3 altogether; as an added benefit,
the Python binaries may be installed in non-standard locations
without the need for updating any PATH variable.
This commit adds the ability to set PYTHON and/or PYTHON_CONFIG
either as environment variables or as make variables on the
command line; the paths may be relative, and usually only PYTHON
is necessary in order for PYTHON_CONFIG to be defined implicitly.
Some rudimentary error checking is performed when the user
explicitly specifies a value for any of these variables.
In addition, this commit introduces significantly robust makefile
infrastructure for working with paths and communicating with the
shell; it's currently only used for handling Python, but I hope
it will prove useful in refactoring the makefiles.
Thanks to:
Raghavendra D Prabhu <rprabhu@wnohang.net>
for motivating this patch.
Acked-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
Link: http://lkml.kernel.org/r/e987828e-87ec-4973-95e7-47f10f5d9bab-mfwitten@gmail.com
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2011-04-03 05:46:09 +08:00
$( python-clean)
2009-04-20 19:32:07 +08:00
.PHONY : all install clean strip
.PHONY : shell_compatibility_test please_set_SHELL_PATH_to_a_more_modern_shell
2009-04-20 21:00:56 +08:00
.PHONY : .FORCE -PERF -VERSION -FILE TAGS tags cscope .FORCE -PERF -CFLAGS
