From: kbuild test robot <lkp@intel.com>
To: Yonghong Song <yhs@fb.com>
Cc: kbuild-all@01.org, peterz@infradead.org, rostedt@goodmis.org,
ast@fb.com, daniel@iogearbox.net, netdev@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH net-next v3 1/4] bpf: add helper bpf_perf_event_read_value for perf event array map
Date: Tue, 19 Sep 2017 14:28:58 +0800 [thread overview]
Message-ID: <201709191400.9qOR1Zdq%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170918230553.1624357-2-yhs@fb.com>
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
Hi Yonghong,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Yonghong-Song/bpf-add-two-helpers-to-read-perf-event-enabled-running-time/20170919-134113
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
kernel/bpf/arraymap.c: In function 'perf_event_fd_array_get_ptr':
>> kernel/bpf/arraymap.c:495:6: error: too many arguments to function 'perf_event_read_local'
if (perf_event_read_local(event, &value, NULL, NULL) == -EOPNOTSUPP)
^
In file included from kernel/bpf/arraymap.c:18:0:
include/linux/perf_event.h:1290:19: note: declared here
static inline int perf_event_read_local(struct perf_event *event, u64 *value)
^
vim +/perf_event_read_local +495 kernel/bpf/arraymap.c
480
481 static void *perf_event_fd_array_get_ptr(struct bpf_map *map,
482 struct file *map_file, int fd)
483 {
484 struct bpf_event_entry *ee;
485 struct perf_event *event;
486 struct file *perf_file;
487 u64 value;
488
489 perf_file = perf_event_get(fd);
490 if (IS_ERR(perf_file))
491 return perf_file;
492
493 ee = ERR_PTR(-EOPNOTSUPP);
494 event = perf_file->private_data;
> 495 if (perf_event_read_local(event, &value, NULL, NULL) == -EOPNOTSUPP)
496 goto err_out;
497
498 ee = bpf_event_entry_gen(perf_file, map_file);
499 if (ee)
500 return ee;
501 ee = ERR_PTR(-ENOMEM);
502 err_out:
503 fput(perf_file);
504 return ee;
505 }
506
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 44401 bytes --]
next prev parent reply other threads:[~2017-09-19 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 23:05 [PATCH net-next v3 0/4] bpf: add two helpers to read perf event enabled/running time Yonghong Song
2017-09-18 23:05 ` [PATCH net-next v3 1/4] bpf: add helper bpf_perf_event_read_value for perf event array map Yonghong Song
2017-09-19 6:28 ` kbuild test robot [this message]
2017-09-18 23:05 ` [PATCH net-next v3 2/4] bpf: add a test case for helper bpf_perf_event_read_value Yonghong Song
2017-09-18 23:05 ` [PATCH net-next v3 3/4] bpf: add helper bpf_perf_prog_read_value Yonghong Song
2017-09-18 23:05 ` [PATCH net-next v3 4/4] bpf: add a test case for " Yonghong Song
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=201709191400.9qOR1Zdq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yhs@fb.com \
/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