From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] perf record: implement --affinity=node|cpu option
Date: Tue, 22 Jan 2019 15:55:04 +0300 [thread overview]
Message-ID: <16d51c60-3964-4ed6-30c7-a414cfdbc089@linux.intel.com> (raw)
In-Reply-To: <20190121115448.GB3852@krava>
On 21.01.2019 14:54, Jiri Olsa wrote:
> On Wed, Jan 16, 2019 at 12:23:56PM +0300, Alexey Budankov wrote:
>>
>> Implement --affinity=node|cpu option for the record mode defaulting
>> to system affinity mask bouncing.
>>
>> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
>> ---
>> changes in v3:
>> - adjusted indentation at record__parse_affinity()
>
> having problems to apply this one:
>
> Applying: perf record: allocate affinity masks
> Applying: perf record: bind the AIO user space buffers to nodes
> Applying: perf record: apply affinity masks when reading mmap buffers
> Applying: perf record: implement --affinity=node|cpu option
> error: corrupt patch at line 62
> Patch failed at 0004 perf record: implement --affinity=node|cpu option
It looks like Arnaldo's perf/core is progressing fast.
Currently I have this thing when building clean Arnaldo's perf/core:
CC tests/hists_output.o
In file included from util/session.c:26:
util/sample-raw.h:9:6: error: redundant redeclaration of perf_evlist__s390_sample_raw [-Werror=redundant-decls]
void perf_evlist__s390_sample_raw(struct perf_evlist *evlist,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from util/session.c:13:
util/evlist.h:321:6: note: previous declaration of perf_evlist__s390_sample_raw was here
void perf_evlist__s390_sample_raw(struct perf_evlist *evlist, union perf_event *event,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC tests/hists_cumulate.o
CC tests/python-use.o
CC util/s390-sample-raw.o
Thanks,
Alexey
>
>
> jirka
>
next prev parent reply other threads:[~2019-01-22 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 9:16 [PATCH v4 0/4] Reduce NUMA related overhead in perf record profiling on large server systems Alexey Budankov
2019-01-16 9:21 ` [PATCH v4 1/4] perf record: allocate affinity masks Alexey Budankov
2019-01-16 9:22 ` [PATCH v4 2/4] perf record: bind the AIO user space buffers to nodes Alexey Budankov
2019-01-16 9:23 ` [PATCH v4 3/4] perf record: apply affinity masks when reading mmap buffers Alexey Budankov
2019-01-21 11:54 ` Jiri Olsa
2019-01-22 12:55 ` Alexey Budankov
2019-01-16 9:23 ` [PATCH v4 4/4] perf record: implement --affinity=node|cpu option Alexey Budankov
2019-01-21 11:54 ` Jiri Olsa
2019-01-22 12:55 ` Alexey Budankov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-10 10:46 [PATCH v4 0/4] Reduce NUMA related overhead in perf record profiling on large server systems Alexey Budankov
2019-01-10 11:24 ` [PATCH v4 4/4] perf record: implement --affinity=node|cpu option Alexey Budankov
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=16d51c60-3964-4ed6-30c7-a414cfdbc089@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@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).