mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@fb.com>
Cc: kbuild-all@01.org, "David S . Miller" <davem@davemloft.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Brendan Gregg <bgregg@netflix.com>,
	Daniel Borkmann <daniel@iogearbox.net>, Teng Qin <qinteng@fb.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types
Date: Fri, 26 May 2017 19:04:30 +0800	[thread overview]
Message-ID: <201705261910.iLtYwiQE%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170526055549.557818-2-ast@fb.com>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

Hi Teng,

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Alexei-Starovoitov/bpf-Add-BPF-support-to-all-perf_event/20170526-171542
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
        wget https://raw.githubusercontent.com/01org/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=ia64 

All errors (new ones prefixed by >>):

   kernel//bpf/arraymap.c: In function 'perf_event_fd_array_get_ptr':
>> kernel//bpf/arraymap.c:466:11: error: 'struct perf_event' has no member named 'attach_state'
     if (event->attach_state & PERF_ATTACH_TASK)
              ^~

vim +466 kernel//bpf/arraymap.c

   460		if (IS_ERR(perf_file))
   461			return perf_file;
   462	
   463		event = perf_file->private_data;
   464		ee = ERR_PTR(-EINVAL);
   465		/* Per-task events are not supported */
 > 466		if (event->attach_state & PERF_ATTACH_TASK)
   467			goto err_out;
   468	
   469		attr = perf_event_attrs(event);

---
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: 47722 bytes --]

  reply	other threads:[~2017-05-26 11:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  5:55 [PATCH v2 net-next 0/3] bpf: Add BPF support to all perf_event Alexei Starovoitov
2017-05-26  5:55 ` [PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types Alexei Starovoitov
2017-05-26 11:04   ` kbuild test robot [this message]
2017-05-26 14:55   ` David Miller
2017-05-29  9:12   ` Peter Zijlstra
2017-05-29  9:39     ` Peter Zijlstra
2017-05-30 15:52       ` Alexei Starovoitov
2017-05-30 16:51         ` Peter Zijlstra
2017-05-30 17:37           ` Alexei Starovoitov
2017-05-30 19:03             ` Peter Zijlstra
2017-06-01 13:32               ` Peter Zijlstra
2017-06-01 15:21                 ` Alexei Starovoitov
2017-05-26  5:55 ` [PATCH v2 net-next 2/3] samples/bpf: add samples for more perf event types Alexei Starovoitov
2017-05-26  5:55 ` [PATCH v2 net-next 3/3] bpf: update perf event helper functions documentation Alexei Starovoitov

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=201705261910.iLtYwiQE%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ast@fb.com \
    --cc=bgregg@netflix.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=qinteng@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

all inboxes | Powered by JetHome®