From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alexei Starovoitov <ast@plumgrid.com>,
<brendan.d.gregg@gmail.com>, <daniel@iogearbox.net>,
<namhyung@kernel.org>, <masami.hiramatsu.pt@hitachi.com>,
<paulus@samba.org>, <a.p.zijlstra@chello.nl>, <mingo@redhat.com>,
<jolsa@kernel.org>, <dsahern@gmail.com>,
<linux-kernel@vger.kernel.org>, <lizefan@huawei.com>,
<hekuang@huawei.com>, <xiakaixu@huawei.com>, <pi3orama@163.com>
Subject: Re: [RFC PATCH v9 02/50] tools build: Add feature check for eBPF API
Date: Wed, 1 Jul 2015 09:23:46 +0800 [thread overview]
Message-ID: <55934122.2020103@huawei.com> (raw)
In-Reply-To: <20150630143452.GA5888@kernel.org>
On 2015/6/30 22:34, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jun 30, 2015 at 10:29:08AM +0800, Wangnan (F) escreveu:
>> On 2015/6/30 3:41, Arnaldo Carvalho de Melo wrote:
>>>> So, what should I do now? I want to have that OFF line turned to "on",
>>>> so that I can test this stuff.
>>>> But the changelog says nothing about it, lemme check the cover letter,
>>>> but having to do that is annoying, one expects to have instructions
>>>> related to some specific changeset in its comments...
>>> So, when such build tests fail, we can see why by looking for a file
>>> with a special name in the O= output dir:
>>> [acme@felicio linux]$ cat /tmp/build/perf/feature/test-bpf.make.output
>>> test-bpf.c:1:23: fatal error: linux/bpf.h: No such file or directory
>>> #include <linux/bpf.h>
>>> ^
>>> compilation terminated.
>>> [acme@felicio linux]$
>
>> This patch tries to check the version of bpf.h, because old bpf.h doesn't
>> define 'kern_version' field for 'union bpf_attr'.
> Ok, I realise it needs to find some bpf.h file, but where should it look
> for it? What needs to be installed so that this feature test succeeds?
>
>> I think the problem you meet is caused by missing of kernel headers in your
>> host system environment. After patch 'perf tools: Make perf depend on
>> libbpf'
> What is precise path to this bpf.h file? What was the cset that
> introduced it and in what upstream branch is it?
The exact bpf.h patch 2/50 trying to find should be
/usr/include/linux/bpf.h, which
can be found from /tmp/build/perf/feature/test-bpf.d:
/tmp/build/perf/feature/test-bpf.bin: test-bpf.c \
/usr/include/stdc-predef.h \
/usr/include/bits/predefs.h \
/usr/include/linux/bpf.h \
/usr/include/linux/types.h \
....
After applying 3/50, due to the setting of FEATURE_CHECK_CFLAGS-bpf, it
becomes /path/to/kernel/include/uapi/linux/bpf.h, so it won't fail again:
/tmp/build/bpf/feature/test-bpf.bin: test-bpf.c \
/usr/include/stdc-predef.h \
/usr/include/bits/predefs.h \
/path/to/kernel/include/uapi/linux/bpf.h \
/path/to/kernel/tools/include/linux/types.h \
...
>> this checking should always success because it adds required headers
>> into MANIFEST and setup FEATURE_CHECK_CFLAGS-bpf.
>>
>> Also, after applying 3/50 you should see this:
> IIRC I tried yesterday, will try again later and let you know, but
> when introducing a feature test, please state what is required to be
> installed in a system so that it can succeed, where to obtain it, etc.
>
> It is possible to figure this out, but sometimes doing that takes time
> that would be beter invested in processing further patches...
>
> - Arnaldo
>
>> # make O=/tmp/build/bpf/ -C tools/lib/bpf/
>
>> Auto-detecting system features:
>> ... libelf: [ on ]
>> ... libelf-getphdrnum: [ on ]
>> ... libelf-mmap: [ on ]
>> ... bpf: [ on ]
>>
>> make: Entering directory `/home/wn/kernel-hydrogen/tools/lib/bpf'
>> CC /tmp/build/bpf/libbpf.o
>> LD /tmp/build/bpf/libbpf-in.o
>> LINK /tmp/build/bpf/libbpf.a
>> LINK /tmp/build/bpf/libbpf.so
>> make: Leaving directory `/home/wn/kernel/tools/lib/bpf'
>>
>> Even if in perf checking bpf should fail in your machine now, checking bpf
>> feature in
>> libbpf should success because when build libbpf I have added following
>> setting to
>> tools/lib/bpf/Makefile:
>>
>> INCLUDES = -I. -I$(srctree)/tools/include
>> -I$(srctree)/arch/$(ARCH)/include/uapi -I$(srctree)/include/uapi
>> FEATURE_CHECK_CFLAGS-bpf = $(INCLUDES)
>>
>> Do you want me to squash 2/30 and 3/50 together and append 'bpf' checker
>> into FEATURE_TESTS in
>> tools/build/Makefile.feature in 23/50? Then there should be less confusion:
>> when compiling perf
>> before 23/50, bpf feature will never be checked then.
>>
>> Thank you.
>>
>>> Right, one of the few things that could explain the failure, but:
>>>
>>> [acme@felicio linux]$ find . -name bpf.h
>>> ./include/linux/bpf.h
>>> ./include/uapi/linux/bpf.h
>>> [acme@felicio linux]$
>>>
>>> So lemme try doing it in place:
>>>
>>> [acme@felicio linux]$ make -C tools/perf/
>>> make: Entering directory `/home/acme/git/linux/tools/perf'
>>> BUILD: Doing 'make -j4' parallel build
>>>
>>> Auto-detecting system features:
>>> ... dwarf: [ on ]
>>> ... glibc: [ on ]
>>> ... gtk2: [ on ]
>>> ... libaudit: [ on ]
>>> ... libbfd: [ on ]
>>> ... libelf: [ on ]
>>> ... libnuma: [ on ]
>>> ... libperl: [ on ]
>>> ... libpython: [ on ]
>>> ... libslang: [ on ]
>>> ... libunwind: [ on ]
>>> ... libdw-dwarf-unwind: [ on ]
>>> ... zlib: [ on ]
>>> ... lzma: [ on ]
>>> ... bpf: [ OFF ]
>>>
>>>
>>> Doesn't work as well :-\
>>>
>>> Looking at the following patches...
>>>
>>> - Arnaldo
next prev parent reply other threads:[~2015-07-01 1:25 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 14:15 [RFC PATCH v9 00/50] perf tools: filtering events using eBPF programs Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 01/50] tracing, perf: Implement BPF programs attached to uprobes Wang Nan
2015-06-27 12:10 ` [PATCH] bpf: Use correct #ifdef controller for trace_call_bpf() Wang Nan
2015-06-27 12:36 ` [PATCH v2] " Wang Nan
2015-06-27 12:11 ` [RFC PATCH v9 01/50 -fix] tracing, perf: Implement BPF programs attached to uprobes Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 02/50] tools build: Add feature check for eBPF API Wang Nan
2015-06-29 19:21 ` Arnaldo Carvalho de Melo
2015-06-29 19:41 ` Arnaldo Carvalho de Melo
2015-06-30 2:29 ` Wangnan (F)
2015-06-30 14:34 ` Arnaldo Carvalho de Melo
2015-07-01 1:23 ` Wangnan (F) [this message]
2015-06-26 14:15 ` [RFC PATCH v9 03/50] bpf tools: Introduce 'bpf' library to tools Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 04/50] bpf tools: Allow caller to set printing function Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 05/50] bpf tools: Open eBPF object file and do basic validation Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 06/50] bpf tools: Read eBPF object from buffer Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 07/50] bpf tools: Check endianness and make libbpf fail early Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 08/50] bpf tools: Iterate over ELF sections to collect information Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 09/50] bpf tools: Collect version and license from ELF sections Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 10/50] bpf tools: Collect map definitions from 'maps' section Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 11/50] bpf tools: Collect symbol table from SHT_SYMTAB section Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 12/50] bpf tools: Collect eBPF programs from their own sections Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 13/50] bpf tools: Collect relocation sections from SHT_REL sections Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 14/50] bpf tools: Record map accessing instructions for each program Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 15/50] bpf tools: Add bpf.c/h for common bpf operations Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 16/50] bpf tools: Create eBPF maps defined in an object file Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 17/50] bpf tools: Relocate eBPF programs Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 18/50] bpf tools: Introduce bpf_load_program() to bpf.c Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 19/50] bpf tools: Load eBPF programs in object files into kernel Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 20/50] bpf tools: Introduce accessors for struct bpf_program Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 21/50] bpf tools: Introduce accessors for struct bpf_object Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 22/50] bpf tools: Link all bpf objects onto a list Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 23/50] perf tools: Make perf depend on libbpf Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 24/50] perf tools: Introduce llvm config options Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 25/50] perf tools: Call clang to compile C source to object code Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 26/50] perf tests: Add LLVM test for eBPF on-the-fly compiling Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 27/50] perf tools: Auto detecting kernel build directory Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 28/50] perf tools: Auto detecting kernel include options Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 29/50] perf record: Enable passing bpf object file to --event Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 30/50] perf record: Compile scriptlets if pass '.c' " Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 31/50] perf tools: Parse probe points of eBPF programs during preparation Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 32/50] perf probe: Attach trace_probe_event with perf_probe_event Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 33/50] perf record: Probe at kprobe points Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 34/50] perf record: Load all eBPF object into kernel Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 35/50] perf tools: Add bpf_fd field to evsel and config it Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 36/50] perf tools: Attach eBPF program to perf event Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 37/50] perf tools: Suppress probing messages when probing by BPF loading Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 38/50] perf record: Add clang options for compiling BPF scripts Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 39/50] bpf tools: Load a program with different instance using preprocessor Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 40/50] perf tools: Fix probe-event.h include Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 41/50] perf probe: Reset tev->args and tev->nargs when failure Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 42/50] perf tools: Move linux/filter.h to tools/include Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 43/50] perf tools: Add BPF_PROLOGUE config options for further patches Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 44/50] perf tools: Introduce arch_get_reg_info() for x86 Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 45/50] perf tools: Add prologue for BPF programs for fetching arguments Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 46/50] perf tools: Generate prologue for BPF programs Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 47/50] perf tools: Use same BPF program if arguments are identical Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 48/50] perf record: Support custom vmlinux path Wang Nan
2015-06-26 14:15 ` [RFC PATCH v9 49/50] perf probe: Init symbol as kprobe if any event is kprobe Wang Nan
2015-06-27 12:25 ` [RFC PATCH v9 49/50 -fix] " Wang Nan
2015-06-29 14:33 ` Arnaldo Carvalho de Melo
2015-06-30 1:38 ` Wangnan (F)
2015-06-30 14:37 ` Arnaldo Carvalho de Melo
2015-07-01 1:31 ` Wangnan (F)
2015-06-26 14:15 ` [RFC PATCH v9 50/50] perf tools: Support attach BPF program on uprobe events Wang Nan
2015-06-26 22:44 ` [RFC PATCH v9 00/50] perf tools: filtering events using eBPF programs Alexei Starovoitov
2015-06-27 0:14 ` Wangnan (F)
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=55934122.2020103@huawei.com \
--to=wangnan0@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=pi3orama@163.com \
--cc=xiakaixu@huawei.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
Powered by JetHome