All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: <ast@plumgrid.com>, <linux-kernel@vger.kernel.org>,
	<lizefan@huawei.com>, <hekuang@huawei.com>, <xiakaixu@huawei.com>,
	<pi3orama@163.com>
Subject: Re: [PATCH 14/39] perf tools: Auto detecting kernel build directory
Date: Tue, 14 Jul 2015 15:16:55 +0800	[thread overview]
Message-ID: <55A4B767.3090202@huawei.com> (raw)
In-Reply-To: <55A4B293.8070200@huawei.com>



On 2015/7/14 14:56, Wangnan (F) wrote:
>
>
> On 2015/7/14 5:46, Arnaldo Carvalho de Melo wrote:
>> Em Thu, Jul 09, 2015 at 12:35:17PM +0000, Wang Nan escreveu:
>>> This patch detects kernel build directory using a embedded shell
>>> script 'kbuild_detector', which does this by checking existence of
>>> include/generated/autoconf.h.
>>>
>>> clang working directory is changed to kbuild directory if it is found,
>>> to help user use relative include path. Following patch will detect
>>> kernel include directory, which contains relative include patch so this
>>> workdir changing is needed.
>>>
>>> Users are allowed to set 'kbuild-dir = ""' manually to disable this
>>> checking.
>> What is the advantage of doing this using a hardcoded shell script,
>> pipes, etc? Why not plain use some asprintf() for the pathnames to be
>> tested, then check those, etc in plain C?
>>
>> I have applied everything up to 13/39, provided some coments to the
>> others, will continue later today/tomorrow.
>>
>> Pushing what I have to perf/ebpf in my tree,
>>
>> Ah, please try, in your csets, to add the CC entries for the people you
>> CC when posting the patches to lkml, so that, when I pull from your
>> tree and then push to Ingo, people get notified, i.e. to follow the
>> style we use in tip/ branches.
>>
>> Right now I am cherry-picking, but at some point I would like to do
>> direct pulls.
>>
>> Thanks,
>>
>> - Arnaldo
>
> Thanks to your reply. I have accepted all of your advise and updated 
> my csets:
>
>  1. Don't use script to check kbuild dir. Instead, use asprintf() + 
> access();
>
>  2. Add CCs in each patches. Commit message of the top two patches in 
> your perf/ebpf
>     is updated.
>
> Other changes including:
>
>  3. Simplify test__llvm using asprintf();
>
>  4. Bugfix: 'bpf tools: Load a program with different instances using 
> preprocessor':
>     1. Add missing '!';
>     2. Allows bpf_program__unload() before the program is loaded to 
> suppress
>        warning message in 'perf test 38'.
>
> The following changes since commit 
> 101ef9b4f5c70dbfffa0186102c1014bd81a4ec7:
>
>   bpf tools: Link all bpf objects onto a list (2015-07-13 18:48:17 -0300)
>
> are available in the git repository at:
>
>   https://github.com/WangNan0/linux.git perf/ebpf-for-acme
>
> for you to fetch changes up to d7425110530a9457f55a44ac01ab81558a5a5cca:
>
up to 7df09f02cba5ded215908e7a4db648966dddec2b.

I added 'Link' fields after CCs.

Thank you.


> perf tools: Support attach BPF program on uprobe events (2015-07-14 
> 06:40:11 +0000)
>
>
> Thank you.



  reply	other threads:[~2015-07-14  7:25 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 12:35 [GIT PULL 00/39] perf tools: filtering events using eBPF programs Wang Nan
2015-07-09 12:35 ` [PATCH 01/39] bpf tools: Collect symbol table from SHT_SYMTAB section Wang Nan
2015-07-09 12:35 ` [PATCH 02/39] bpf tools: Collect eBPF programs from their own sections Wang Nan
2015-07-09 15:58   ` Arnaldo Carvalho de Melo
2015-07-10  3:07     ` Wangnan (F)
2015-07-13 19:51       ` Arnaldo Carvalho de Melo
2015-07-14  3:58         ` Wangnan (F)
2015-07-09 12:35 ` [PATCH 03/39] bpf tools: Collect relocation sections from SHT_REL sections Wang Nan
2015-07-09 12:35 ` [PATCH 04/39] bpf tools: Record map accessing instructions for each program Wang Nan
2015-07-09 12:35 ` [PATCH 05/39] bpf tools: Add bpf.c/h for common bpf operations Wang Nan
2015-07-09 12:35 ` [PATCH 06/39] bpf tools: Create eBPF maps defined in an object file Wang Nan
2015-07-13 19:54   ` Arnaldo Carvalho de Melo
2015-07-14  3:59     ` Wangnan (F)
2015-07-09 12:35 ` [PATCH 07/39] bpf tools: Relocate eBPF programs Wang Nan
2015-07-09 12:35 ` [PATCH 08/39] bpf tools: Introduce bpf_load_program() to bpf.c Wang Nan
2015-07-09 12:35 ` [PATCH 09/39] bpf tools: Load eBPF programs in object files into kernel Wang Nan
2015-07-09 12:35 ` [PATCH 10/39] bpf tools: Introduce accessors for struct bpf_program Wang Nan
2015-07-09 12:35 ` [PATCH 11/39] bpf tools: Link all bpf objects onto a list Wang Nan
2015-07-09 12:35 ` [PATCH 12/39] perf tools: Introduce llvm config options Wang Nan
2015-07-21 11:13   ` [PATCH 12/39 update] " Wang Nan
2015-08-08  8:16     ` [tip:perf/core] " tip-bot for Wang Nan
2015-07-09 12:35 ` [PATCH 13/39] perf tools: Call clang to compile C source to object code Wang Nan
2015-07-09 12:35 ` [PATCH 14/39] perf tools: Auto detecting kernel build directory Wang Nan
2015-07-13 21:46   ` Arnaldo Carvalho de Melo
2015-07-14  6:56     ` Wangnan (F)
2015-07-14  7:16       ` Wangnan (F) [this message]
2015-07-09 12:35 ` [PATCH 15/39] perf tools: Auto detecting kernel include options Wang Nan
2015-08-08  8:17   ` [tip:perf/core] " tip-bot for Wang Nan
2015-07-09 12:35 ` [PATCH 16/39] perf tests: Add LLVM test for eBPF on-the-fly compiling Wang Nan
2015-07-15 10:54   ` [PATCH updated " Wang Nan
2015-07-22  4:46   ` [PATCH 16/39 RESEND] " Wang Nan
2015-07-09 12:35 ` [PATCH 17/39] perf tools: Make perf depend on libbpf Wang Nan
2015-07-09 12:35 ` [PATCH 18/39] perf record: Enable passing bpf object file to --event Wang Nan
2015-07-09 12:35 ` [PATCH 19/39] perf record: Compile scriptlets if pass '.c' " Wang Nan
2015-07-09 12:35 ` [PATCH 20/39] perf tools: Parse probe points of eBPF programs during preparation Wang Nan
2015-07-09 12:35 ` [PATCH 21/39] perf probe: Attach trace_probe_event with perf_probe_event Wang Nan
2015-07-09 12:35 ` [PATCH 22/39] perf record: Probe at kprobe points Wang Nan
2015-07-09 12:35 ` [PATCH 23/39] perf record: Load all eBPF object into kernel Wang Nan
2015-07-09 12:35 ` [PATCH 24/39] perf tools: Add bpf_fd field to evsel and config it Wang Nan
2015-07-09 12:35 ` [PATCH 25/39] perf tools: Attach eBPF program to perf event Wang Nan
2015-07-09 12:35 ` [PATCH 26/39] perf tools: Suppress probing messages when probing by BPF loading Wang Nan
2015-07-09 12:35 ` [PATCH 27/39] perf record: Add clang options for compiling BPF scripts Wang Nan
2015-07-09 12:35 ` [PATCH 28/39] bpf tools: Load a program with different instances using preprocessor Wang Nan
2015-07-13  5:44   ` Wangnan (F)
2015-07-09 12:35 ` [PATCH 29/39] perf tools: Fix probe-event.h include Wang Nan
2015-07-09 12:35 ` [PATCH 30/39] perf probe: Reset args and nargs for probe_trace_event when failure Wang Nan
2015-07-09 12:35 ` [PATCH 31/39] perf tools: Move linux/filter.h to tools/include Wang Nan
2015-07-09 12:35 ` [PATCH 32/39] perf tools: Add BPF_PROLOGUE config options for further patches Wang Nan
2015-07-09 12:35 ` [PATCH 33/39] perf tools: Introduce arch_get_reg_info() for x86 Wang Nan
2015-07-09 12:35 ` [PATCH 34/39] perf tools: Add prologue for BPF programs for fetching arguments Wang Nan
2015-07-09 12:35 ` [PATCH 35/39] perf tools: Generate prologue for BPF programs Wang Nan
2015-07-09 12:35 ` [PATCH 36/39] perf tools: Use same BPF program if arguments are identical Wang Nan
2015-07-09 12:35 ` [PATCH 37/39] perf record: Support custom vmlinux path Wang Nan
2015-07-09 12:35 ` [PATCH 38/39] perf probe: Init symbol as kprobe if any event is kprobe Wang Nan
2015-07-09 12:35 ` [PATCH 39/39] perf tools: Support attach BPF program on uprobe events Wang Nan
2015-07-14 15:36 ` perf test LLVM was: Re: [GIT PULL 00/39] perf tools: filtering events using eBPF programs Arnaldo Carvalho de Melo
2015-07-15 10:49   ` Wangnan (F)
2015-07-15 11:20     ` Arnaldo Carvalho de Melo
2015-07-17  2:34       ` Wangnan (F)
     [not found]         ` <CA+JHD93=ZMFP0gB1NqTXGBjTfSyYC-53Uj7r11gQJnKtQRKcDg@mail.gmail.com>
2015-07-21 11:09           ` Wangnan (F)
2015-07-21 11:41             ` Arnaldo Carvalho de Melo
2015-07-22  4:40               ` Wangnan (F)
2015-07-31 15:35                 ` perf eBPF patch ordering. was: " Arnaldo Carvalho de Melo
2015-07-31 20:31                   ` Arnaldo Carvalho de Melo
2015-08-03  2:37                     ` Wangnan (F)
2015-08-03 15:07                       ` Arnaldo Carvalho de Melo
2015-08-03 15:19                         ` Arnaldo Carvalho de Melo
2015-08-03 15:53                           ` pi3orama
2015-08-03 16:11                             ` Arnaldo Carvalho de Melo
2015-08-03 19:49                               ` Arnaldo Carvalho de Melo
2015-08-04  5:28                                 ` Wangnan (F)
2015-08-04 10:39                                   ` Wangnan (F)
2015-08-04 15:55                                     ` Arnaldo Carvalho de Melo
2015-08-04 16:11                                       ` Arnaldo Carvalho de Melo
2015-08-04 16:13                                         ` pi3orama
2015-08-06  1:44                                         ` Wangnan (F)
2015-08-06 14:46                                           ` Arnaldo Carvalho de Melo
2015-08-06 15:58                                             ` Arnaldo Carvalho de Melo

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=55A4B767.3090202@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@kernel.org \
    --cc=ast@plumgrid.com \
    --cc=hekuang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.