From: "Wangnan (F)" <wangnan0@huawei.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: <acme@redhat.com>, <linux-kernel@vger.kernel.org>,
<pi3orama@163.com>, <lizefan@huawei.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] tools build: Remove FEATURE-DUMP
Date: Fri, 18 Dec 2015 16:41:05 +0800 [thread overview]
Message-ID: <5673C6A1.2090109@huawei.com> (raw)
In-Reply-To: <20151207135254.GC26191@krava.brq.redhat.com>
On 2015/12/7 21:52, Jiri Olsa wrote:
> On Mon, Dec 07, 2015 at 10:48:58AM +0000, Wang Nan wrote:
>> Jiri introduces a FEATURE-INCLUDE file for feature checking. It
>> contains same information with FEATURE-DUMP, so we can avoid generating
>> FEATURE-DUMP.
>>
>> Following modification should ensure FEATURE_TESTS contains
>> FEATURE_DISPLAY.
>>
>> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>> Cc: Jiri Olsa <jolsa@kernel.org>
>> ---
>>
>> I haven't thoroughly tested this patch, just want to show the
>> possibility of removing FEATURE-DUMP. I don't insist on this. Jiri, if
>> you find this patch is not good please simply ignore it.
>>
>> Thank you.
>>
>> ---
>>
>> tools/build/Makefile.feature | 8 +++-----
>> tools/lib/bpf/.gitignore | 1 -
>> tools/lib/bpf/Makefile | 2 +-
>> tools/perf/.gitignore | 1 -
>> tools/perf/Makefile.perf | 2 +-
>> 5 files changed, 5 insertions(+), 9 deletions(-)
>>
>> diff --git a/tools/build/Makefile.feature b/tools/build/Makefile.feature
>> index 51f8d59..98a13bd 100644
>> --- a/tools/build/Makefile.feature
>> +++ b/tools/build/Makefile.feature
>> @@ -123,10 +123,6 @@ define feature_print_text_code
>> MSG = $(shell printf '...%30s: %s' $(1) $(2))
>> endef
>>
>> -FEATURE_DUMP_FILENAME = $(OUTPUT)FEATURE-DUMP$(FEATURE_USER)
>> -FEATURE_DUMP := $(foreach feat,$(FEATURE_DISPLAY),feature-$(feat)($(feature-$(feat))))
>> -FEATURE_DUMP_FILE := $(shell touch $(FEATURE_DUMP_FILENAME); cat $(FEATURE_DUMP_FILENAME))
>> -
>> ifeq ($(dwarf-post-unwind),1)
>> FEATURE_DUMP += dwarf-post-unwind($(dwarf-post-unwind-text))
>> endif
>> @@ -141,6 +137,9 @@ endif
>> # features detection state.
>> FEATURE_INCLUDE_FILENAME = $(OUTPUT)FEATURE-INCLUDE$(FEATURE_USER)
>>
>> +FEATURE_DUMP := $(foreach feat,$(FEATURE_DISPLAY),feature-$(feat)=$(feature-$(feat)))
>> +FEATURE_DUMP_FILE := $(foreach feat,$(FEATURE_DISPLAY),$(shell touch $(FEATURE_INCLUDE_FILENAME); cat $(FEATURE_INCLUDE_FILENAME) | grep 'feature-$(feat)='))
> hum, this ignores dwarf-post-unwind setup, I think it needs more changes
> I'll post new version
Hi Jiri,
What the current status of this patch and 'tools build: Introduce
features dump include makefile'? They are in my local tree for a long time.
Thank you.
next prev parent reply other threads:[~2015-12-18 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 9:06 [PATCH 1/2] tools build: Introduce features dump include makefile Jiri Olsa
2015-11-27 9:06 ` [PATCH 2/2] perf build: Use FEATURE-INCLUDE in bpf subproject Jiri Olsa
2015-12-07 8:56 ` [PATCH 1/2] tools build: Introduce features dump include makefile Jiri Olsa
2015-12-07 9:22 ` Wangnan (F)
2015-12-07 10:29 ` Jiri Olsa
2015-12-07 10:32 ` Wangnan (F)
2015-12-07 10:38 ` Wangnan (F)
2015-12-07 10:48 ` [PATCH] tools build: Remove FEATURE-DUMP Wang Nan
2015-12-07 13:52 ` Jiri Olsa
2015-12-18 8:41 ` Wangnan (F) [this message]
2015-12-18 10:13 ` Jiri Olsa
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=5673C6A1.2090109@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox