From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v1 2/3] perf version: Print the status of compiled-in libraries
Date: Tue, 27 Mar 2018 09:44:23 +0800 [thread overview]
Message-ID: <6496ab3e-47a4-69ac-76da-18f0b228581f@linux.intel.com> (raw)
In-Reply-To: <20180326093925.GI6207@krava>
On 3/26/2018 5:39 PM, Jiri Olsa wrote:
> On Tue, Mar 27, 2018 at 12:07:03AM +0800, Jin Yao wrote:
>> This patch checks the values passed by CFLAGS (-DXXX) and then
>> print the status of libraries.
>>
>> For example, if HAVE_DWARF_SUPPORT is defined, that means the
>> library "dwarf" is compiled-in. The patch will print the status
>> "on" for this library.
>>
>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>> ---
>> tools/perf/builtin-version.c | 125 +++++++++++++++++++++++++++++++++++++++++++
>> tools/perf/builtin.h | 1 +
>> 2 files changed, 126 insertions(+)
>>
>> diff --git a/tools/perf/builtin-version.c b/tools/perf/builtin-version.c
>> index 37019c5..90a0a7f 100644
>> --- a/tools/perf/builtin-version.c
>> +++ b/tools/perf/builtin-version.c
>> @@ -9,3 +9,128 @@ int cmd_version(int argc __maybe_unused, const char **argv __maybe_unused)
>> printf("perf version %s\n", perf_version_string);
>> return 0;
>> }
>> +
>> +static void status_print(const char *name, const char *status)
>> +{
>> + printf("%22s: [ %3s ]\n", name, status);
>> +}
>> +
>> +static void library_status(void)
>> +{
>> +#ifdef HAVE_DWARF_SUPPORT
>> + status_print("dwarf", "on");
>> +#else
>> + status_print("dwarf", "off");
>> +#endif
>
> could this and all those below be in some generic macro?
>
> #define STATUS(__d, __m) \
> #ifdef __d \
> status_print(#__m, "on"); \
> #else \
> status_print(#__m, "OFF"); \
> #endif
>
> STATUS(HAVE_DWARF_SUPPORT, dwarf)
>
>
Hi Jiri,
I have tried this macro definition, but unfortunately the compilation is
failed.
error: '#' is not followed by a macro parameter
#define STATUS(__d, __m) \
I just guess the '#' in #ifdef confuses the gcc. Looks we can't define
#ifdef/#endif block in a macro.
Thanks
Jin Yao
> also please print the 'OFF' and use colors as in the build message
>
>> +
>> +#ifdef HAVE_DWARF_GETLOCATIONS
>> + status_print("dwarf_getlocations", "on");
>> +#else
>> + status_print("dwarf_getlocations", "off");
>> +#endif
>> +
>> +#ifdef NO_GLIBC
>> + status_print("glibc", "off");
>> +#else
>> + status_print("glibc", "on");
>> +#endif
>> +
>> +#ifdef HAVE_GTK2_SUPPORT
>> + status_print("gtk2", "on");
>> +#else
>> + status_print("gtk2", "off");
>> +#endif
>> +
>
> SNIP
>
>> +}
>> +
>> +int cmd_version2(int argc, const char **argv)
>> +{
>> + cmd_version(argc, argv);
>> + library_status();
>> + return 0;
>> +}
>> diff --git a/tools/perf/builtin.h b/tools/perf/builtin.h
>> index 05745f3..c7508ee 100644
>> --- a/tools/perf/builtin.h
>> +++ b/tools/perf/builtin.h
>> @@ -29,6 +29,7 @@ int cmd_timechart(int argc, const char **argv);
>> int cmd_top(int argc, const char **argv);
>> int cmd_script(int argc, const char **argv);
>> int cmd_version(int argc, const char **argv);
>> +int cmd_version2(int argc, const char **argv);
>
> please don't add new command for this, handle this in cmd_version
>
> thanks,
> jirka
>
next prev parent reply other threads:[~2018-03-27 1:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 16:07 [PATCH v1 0/3] Support perf -vv Jin Yao
2018-03-26 9:00 ` Andi Kleen
2018-03-26 9:07 ` Jiri Olsa
2018-03-26 13:06 ` Jin, Yao
2018-03-26 16:07 ` [PATCH v1 1/3] perf config: Add -DNO_GLIBC to CFLAGS Jin Yao
2018-03-26 16:07 ` [PATCH v1 2/3] perf version: Print the status of compiled-in libraries Jin Yao
2018-03-26 9:39 ` Jiri Olsa
2018-03-26 13:51 ` Jin, Yao
2018-03-27 3:04 ` Jin, Yao
2018-03-27 12:38 ` Jiri Olsa
2018-03-27 13:26 ` Jin, Yao
2018-03-27 1:44 ` Jin, Yao [this message]
2018-03-27 12:56 ` Jiri Olsa
2018-03-27 13:17 ` Jin, Yao
2018-03-27 13:35 ` Jiri Olsa
2018-03-27 5:58 ` Ingo Molnar
2018-03-27 6:04 ` Jin, Yao
2018-03-26 16:07 ` [PATCH v1 3/3] perf: Support perf -vv Jin Yao
2018-03-27 6:03 ` Ingo Molnar
2018-03-27 6:12 ` Jin, Yao
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=6496ab3e-47a4-69ac-76da-18f0b228581f@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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