From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: peterz@infradead.org, jolsa@kernel.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
bp@suse.de, linux-arch@vger.kernel.org,
Alexey.Brodkin@synopsys.com
Subject: Re: [PATCH 0/5] Perf fixes for ARC + uClibc
Date: Tue, 6 Jan 2015 13:13:29 -0200 [thread overview]
Message-ID: <20150106151329.GD2517@redhat.com> (raw)
In-Reply-To: <1420552335-26886-1-git-send-email-vgupta@synopsys.com>
Em Tue, Jan 06, 2015 at 07:22:10PM +0530, Vineet Gupta escreveu:
> Hi,
>
> This series based off linux-next of 20150105 allows us to build/use perf
> for ARC with uClibc based userland.
Do you have some ready made ARC VM image with devel tools I could use with qemu?
- Arnaldo
> * 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.
>
> 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 +++++
> tools/perf/perf-sys.h | 1 -
> tools/perf/util/cache.h | 2 ++
> tools/perf/util/header.c | 2 +-
> 11 files changed, 33 insertions(+), 6 deletions(-)
>
> --
> 1.9.1
next prev parent reply other threads:[~2015-01-06 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 13:52 [PATCH 0/5] Perf fixes for ARC + uClibc Vineet Gupta
2015-01-06 13:52 ` [PATCH 1/5] perf tools: [uclibc] fix statfs.f_type data type mismatch build error Vineet Gupta
2015-01-06 13:52 ` [PATCH 2/5] perf tools: [uclibc] Elide strlcpy warning Vineet Gupta
2015-01-06 13:52 ` [PATCH 3/5] perf tools: [uclibc] Avoid build splat for syscall numbers Vineet Gupta
2015-01-06 13:52 ` [PATCH 4/5] perf tools: [uclibc] don't rely on glibc malloc working for sz 0 Vineet Gupta
2015-01-08 7:51 ` Namhyung Kim
2015-01-10 10:16 ` Vineet Gupta
2015-01-10 10:44 ` Namhyung Kim
2015-01-06 13:52 ` [PATCH 5/5] perf tools: [uclibc] provide stub for pthread_attr_setaffinity_np Vineet Gupta
2015-01-08 7:56 ` Namhyung Kim
2015-01-10 10:30 ` Vineet Gupta
2015-01-06 15:13 ` Arnaldo Carvalho de Melo [this message]
2015-01-07 5:16 ` [PATCH 0/5] Perf fixes for ARC + uClibc Vineet Gupta
2015-01-07 7:38 ` Vineet Gupta
2015-01-09 18:47 ` Alexey Brodkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150106151329.GD2517@redhat.com \
--to=acme@redhat.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=bp@suse.de \
--cc=jolsa@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).