All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wangnan (F)" <wangnan0@huawei.com>
To: Jiri Olsa <jolsa@kernel.org>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	pi3orama <pi3orama@163.com>, <lizefan@huawei.com>
Subject: Re: [PATCH 0/5] tools build: Make FEATURE_DUMP include makefile
Date: Thu, 24 Dec 2015 10:52:18 +0800	[thread overview]
Message-ID: <567B5DE2.9020900@huawei.com> (raw)
In-Reply-To: <1450893514-9158-1-git-send-email-jolsa@kernel.org>



On 2015/12/24 1:58, Jiri Olsa wrote:
> hi,
> Changing the contents of the FEATURE-DUMP file,
> so it looks like:
>      
>    feature-backtrace=1
>    feature-dwarf=0
>    feature-fortify-source=1
>    feature-sync-compare-and-swap=0
>      
> This way it could get included in sub projects,
> so they won't be forced to redo features detection.
>
> changing bpf library to use that, so it's not forced
> to rerun feature detection if compiled within perf.
>
> Also available in:
>    git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
>
> thanks,
> jirka

Tested-by: Wang Nan <wangnan0@huawei.com>

For the whole patch set.

Thank you.

>
> ---
> Jiri Olsa (5):
>        tools build feature: Fix feature_check_display_code typo
>        tools build feature: Move dwarf post unwind choice output into perf
>        tools build feature: Introduce feature_ass macro
>        tools build feature: Use value assignment form for FEATURE-DUMP file
>        perf build: Use FEATURE-DUMP in bpf subproject
>
>   tools/build/Makefile.feature | 41 +++++++++++++++++++++++++++--------------
>   tools/lib/bpf/Makefile       |  4 ++++
>   tools/perf/Makefile.perf     |  2 +-
>   tools/perf/config/Makefile   |  4 ++++
>   4 files changed, 36 insertions(+), 15 deletions(-)



  parent reply	other threads:[~2015-12-24  2:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 17:58 [PATCH 0/5] tools build: Make FEATURE_DUMP include makefile Jiri Olsa
2015-12-23 17:58 ` [PATCH 1/5] tools build feature: Fix feature_check_display_code typo Jiri Olsa
2016-01-09 16:26   ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-23 17:58 ` [PATCH 2/5] tools build feature: Move dwarf post unwind choice output into perf Jiri Olsa
2016-01-09 16:27   ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-23 17:58 ` [PATCH 3/5] tools build feature: Introduce feature_ass macro Jiri Olsa
2016-01-09 16:27   ` [tip:perf/core] tools build feature: Introduce feature_assign macro tip-bot for Jiri Olsa
2015-12-23 17:58 ` [PATCH 4/5] tools build feature: Use value assignment form for FEATURE-DUMP file Jiri Olsa
2016-01-09 16:27   ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-23 17:58 ` [PATCH 5/5] perf build: Use FEATURE-DUMP in bpf subproject Jiri Olsa
2016-01-09 16:28   ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-24  2:52 ` Wangnan (F) [this message]
2015-12-27 11:58   ` [PATCH 0/5] tools build: Make FEATURE_DUMP include makefile Jiri Olsa
2016-01-04 21:06     ` 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=567B5DE2.9020900@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=pi3orama@163.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.