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 v3 2/4] perf record: bind the AIO user space buffers to nodes
Date: Wed, 9 Jan 2019 19:58:14 +0300 [thread overview]
Message-ID: <75316888-2c63-bbe4-7b2d-2e87ea5102c6@linux.intel.com> (raw)
In-Reply-To: <20190109155853.GA19455@krava>
Hi,
On 09.01.2019 18:58, Jiri Olsa wrote:
> On Wed, Jan 09, 2019 at 12:37:17PM +0300, Alexey Budankov wrote:
>>
>> Allocate and bind AIO user space buffers to the memory nodes
>> that mmap kernel buffers are bound to.
<SNIP>
>>
>> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
<SNIP>
>> +static void perf_mmap__aio_bind(struct perf_mmap *map, int index, int cpu, int affinity)
>> +{
>> + void *data;
>> + size_t mmap_len;
>> + unsigned long node_mask;
>> +
>> + if (affinity != PERF_AFFINITY_SYS && cpu__max_node() > 1) {
>> + data = map->aio.data[index];
>> + mmap_len = perf_mmap__mmap_len(map);
>> + node_mask = 1UL << cpu__get_node(cpu);
>> + if (mbind(data, mmap_len, MPOL_BIND, &node_mask, 1, 0)) {
>> + pr_warn("failed to bind [%p-%p] to node %d\n",
>> + data, data + mmap_len, cpu__get_node(cpu));
>> + }
>
> getting compilation fail in here:
>
> CC util/mmap.o
> util/mmap.c: In function ‘perf_mmap__aio_bind’:
> util/mmap.c:193:4: error: implicit declaration of function ‘pr_warn’; did you mean ‘pr_warning’? [-Werror=implicit-function-declaration]
> pr_warn("failed to bind [%p-%p] to node %d\n",
> ^~~~~~~
> pr_warning
> util/mmap.c:193:4: error: nested extern declaration of ‘pr_warn’ [-Werror=nested-externs]
> cc1: all warnings being treated as errors
Yes, it should be pr_warning().
This hunk missed when I was preparing the patches - sorry.
It will be included into v4.
Thanks!
Alexey
>
>
> jirka
>
next prev parent reply other threads:[~2019-01-09 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 9:19 [PATCH v3 0/4] Reduce NUMA related overhead in perf record profiling on large server systems Alexey Budankov
2019-01-09 9:35 ` [PATCH v3 1/4] perf record: allocate affinity masks Alexey Budankov
2019-01-09 9:37 ` [PATCH v3 2/4] perf record: bind the AIO user space buffers to nodes Alexey Budankov
2019-01-09 15:58 ` Jiri Olsa
2019-01-09 16:58 ` Alexey Budankov [this message]
2019-01-09 9:38 ` [PATCH v3 3/4] perf record: apply affinity masks when reading mmap buffers Alexey Budankov
2019-01-09 16:53 ` Jiri Olsa
2019-01-10 9:41 ` Alexey Budankov
2019-01-10 9:54 ` Jiri Olsa
2019-01-10 10:19 ` Alexey Budankov
2019-01-09 9:40 ` [PATCH v3 4/4] perf record: implement --affinity=node|cpu option Alexey Budankov
2019-01-09 14:41 ` [PATCH v3 0/4] Reduce NUMA related overhead in perf record profiling on large server systems Jiri Olsa
2019-01-09 15:51 ` Jiri Olsa
2019-01-09 16:11 ` 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=75316888-2c63-bbe4-7b2d-2e87ea5102c6@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
Powered by JetHome