[PATCH v2 0/5] Perf tool fixes for ARC + uClibc

From: Vineet Gupta
Date: Sat Jan 10 2015 - 06:11:23 EST


Hi,

This series based off linux-next of 20150105 allows us to build/use perf
for ARC with uClibc based userland.

v2: Change since v1 [1]

* [1-3]/5 : no changes
* 4/5 : Make perf_evsel__alloc_id agnostic of zero threads [Namhyung Kim]
* 5/5 : Add missing test file

v1:
* 1/5 is really a resend of old patch posted by Alexey a while back
* 2/5 is uClibc build spew seen on ARM as well
* 3/5 likewise
* 4/5 is uClibc config specific
* 5/5 is uClibc pthread library flavour specific
It adds a stub for pthread_attr_setaffinity_np
I can rework it to disable the futex tests altogether if people think that is
cleaner

Please review and consider applying.
W/o these perf doesn't build and/or work for ARC.

[1] http://www.spinics.net/linux/lists/kernel/msg1897268.html

Thx,
-Vineet

Alexey Brodkin (1):
perf tools: [uclibc] fix statfs.f_type data type mismatch build error

Vineet Gupta (4):
perf tools: [uclibc] Elide strlcpy warning
perf tools: [uclibc] Avoid build splat for syscall numbers
perf tools: [uclibc] don't rely on glibc malloc working for sz 0
perf tools: [uclibc] provide stub for pthread_attr_setaffinity_np

tools/lib/api/fs/debugfs.c | 2 +-
tools/lib/api/fs/fs.c | 2 +-
tools/perf/bench/futex.h | 13 +++++++++++++
tools/perf/bench/sched-pipe.c | 1 -
tools/perf/builtin-top.c | 1 -
tools/perf/config/Makefile | 6 ++++++
tools/perf/config/feature-checks/Makefile | 4 ++++
tools/perf/config/feature-checks/test-all.c | 5 +++++
.../feature-checks/test-pthread-attr-setaffinity-np.c | 14 ++++++++++++++
tools/perf/perf-sys.h | 1 -
tools/perf/util/cache.h | 2 ++
tools/perf/util/evsel.c | 3 +++
12 files changed, 49 insertions(+), 5 deletions(-)
create mode 100644 tools/perf/config/feature-checks/test-pthread-attr-setaffinity-np.c

--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/