Skip to contentSkip to conversation

perf evsel: Move fprintf methods to separate source file

tip:perf/core tip-bot for Arnaldo Carvalho de Melo 1 participant 1 message Apr 16, 2016 perf events

lore
Share & tools
lore
#0 lore raw
Commit-ID:  25da4fab5f66e659da768cd61dbf8c3861104d7c
Gitweb:     http://git.kernel.org/tip/25da4fab5f66e659da768cd61dbf8c3861104d7c
Author:     Arnaldo Carvalho de Melo <[email protected]>
AuthorDate: Thu, 14 Apr 2016 19:45:01 -0300
Committer:  Arnaldo Carvalho de Melo <[email protected]>
CommitDate: Thu, 14 Apr 2016 19:46:58 -0300

perf evsel: Move fprintf methods to separate source file

They still use functions that would drag more stuff to the python binding, where these fprintf methods are not used, so separate it.

---
 tools/perf/util/Build           |   1 +
 tools/perf/util/evsel.c         | 206 --------------------------------------
 tools/perf/util/evsel_fprintf.c | 212 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 213 insertions(+), 206 deletions(-)
tools/perf/util/Build +1 -0
index 6102133..85a9ab6 100644
@@ -8,6 +8,7 @@ libperf-y += env.o
 libperf-y += event.o
 libperf-y += evlist.o
 libperf-y += evsel.o
+libperf-y += evsel_fprintf.o
 libperf-y += find_bit.o
 libperf-y += kallsyms.o
 libperf-y += levenshtein.o
tools/perf/util/evsel.c +0 -206

212 lines not on this page · raw message

tools/perf/util/evsel_fprintf.c new file +212 -0

212 lines not on this page · raw message