From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH V10 01/13] perf tools: add debug prints
Date: Wed, 14 Aug 2013 14:05:07 +0300 [thread overview]
Message-ID: <520B6463.1010209@intel.com> (raw)
In-Reply-To: <87eh9ywbad.fsf@sejong.aot.lge.com>
On 13/08/13 05:54, Namhyung Kim wrote:
> On Fri, 9 Aug 2013 13:51:47 +0300, Adrian Hunter wrote:
>> It is useful to see the arguments to perf_event_open
>> and whether the perf events ring buffer was mmapped
>> per-cpu or per-thread. That information will now be
>> displayed when verbose is 2 i.e option -vv
>
> I have two nitpicks below, but other than that it looks good, so
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
>
>
> [SNIP]
>
>> +#define __PRINT_ATTR(fmt, cast, field) \
>> + fprintf(fp, " %-19s "fmt"\n", #field, cast attr->field)
>> +
>> +#define PRINT_ATTR_U32(field) __PRINT_ATTR("%u" , , field)
>> +#define PRINT_ATTR_X32(field) __PRINT_ATTR("%#x", , field)
>> +#define PRINT_ATTR_U64(field) __PRINT_ATTR("%" PRIu64, (uint64_t), field)
>> +#define PRINT_ATTR_X64(field) __PRINT_ATTR("%#"PRIx64, (uint64_t), field)
>> +
>> +#define PRINT_ATTR2N(name1, field1, name2, field2) \
>> + fprintf(fp, " %-19s %u %-19s %u\n", \
>> + name1, attr->field1, name2, attr->field2)
>> +
>> +#define PRINT_ATTR2(field1, field2) \
>> + PRINT_ATTR2N(#field1, field1, #field2, field2)
>> +
>> +static size_t perf_event_attr__fprintf(struct perf_event_attr *attr, FILE *fp)
>> +{
>> + size_t ret = 0;
>> +
>> + ret += fprintf(fp, "------------------------------");
>> + ret += fprintf(fp, "------------------------------\n");
>
> We have 'graph_dotted_line' for this.
>
>
>> + ret += fprintf(fp, "perf_event_attr:\n");
>> +
>> + ret += PRINT_ATTR_U32(type);
>> + ret += PRINT_ATTR_U32(size);
>> + ret += PRINT_ATTR_X64(config);
>> + ret += PRINT_ATTR_U64(sample_period);
>> + ret += PRINT_ATTR_U64(sample_freq);
>> + ret += PRINT_ATTR_X64(sample_type);
>> + ret += PRINT_ATTR_X64(read_format);
>> +
>> + ret += PRINT_ATTR2(disabled, inherit);
>> + ret += PRINT_ATTR2(pinned, exclusive);
>> + ret += PRINT_ATTR2(exclude_user, exclude_kernel);
>> + ret += PRINT_ATTR2(exclude_hv, exclude_idle);
>> + ret += PRINT_ATTR2(mmap, comm);
>> + ret += PRINT_ATTR2(freq, inherit_stat);
>> + ret += PRINT_ATTR2(enable_on_exec, task);
>> + ret += PRINT_ATTR2(watermark, precise_ip);
>> + ret += PRINT_ATTR2(mmap_data, sample_id_all);
>> + ret += PRINT_ATTR2(exclude_host, exclude_guest);
>> + ret += PRINT_ATTR2N("excl.callchain_kern", exclude_callchain_kernel,
>> + "excl.callchain_user", exclude_callchain_user);
>> +
>> + ret += PRINT_ATTR_U32(wakeup_events);
>> + ret += PRINT_ATTR_U32(wakeup_watermark);
>> + ret += PRINT_ATTR_X32(bp_type);
>> + ret += PRINT_ATTR_X64(bp_addr);
>> + ret += PRINT_ATTR_X64(config1);
>> + ret += PRINT_ATTR_U64(bp_len);
>> + ret += PRINT_ATTR_X64(config2);
>> + ret += PRINT_ATTR_X64(branch_sample_type);
>> + ret += PRINT_ATTR_X64(sample_regs_user);
>> + ret += PRINT_ATTR_U32(sample_stack_user);
>> +
>> + ret += fprintf(fp, "------------------------------");
>> + ret += fprintf(fp, "------------------------------\n");
>> +
>> + return ret;
>> +}
>
> [SNIP]
>
>> diff --git a/tools/perf/util/python.c b/tools/perf/util/python.c
>> index 925e0c3..381f4fd 100644
>> --- a/tools/perf/util/python.c
>> +++ b/tools/perf/util/python.c
>> @@ -8,6 +8,26 @@
>> #include "cpumap.h"
>> #include "thread_map.h"
>>
>> +/*
>> + * Support debug printing even though util/debug.c is not linked. That means
>> + * implementing 'verbose' and 'eprintf'.
>> + */
>> +int verbose;
>> +
>> +int eprintf(int level, const char *fmt, ...)
>> +{
>> + va_list args;
>> + int ret = 0;
>> +
>> + if (verbose >= level) {
>> + va_start(args, fmt);
>> + ret = vfprintf(stderr, fmt, args);
>> + va_end(args);
>> + }
>> +
>> + return ret;
>> +}
>
> Not sure this duplication is the right way. Maybe linking util/debug.c
> into the python extension and move trace_event() somewhere is a better
> approach. But it'd make the util/debug.c more fragile?
trace_event is not the problem. ui_helpline__vshow is. So eprintf has to be
re-implemented anyway.
>
> Anyway this change could be splitted as a preparation patch.
>
> Thanks,
> Namhyung
>
>
next prev parent reply other threads:[~2013-08-14 10:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 10:51 [PATCH V10 00/13] perf tools: some fixes and tweaks Adrian Hunter
2013-08-09 10:51 ` [PATCH V10 01/13] perf tools: add debug prints Adrian Hunter
2013-08-13 2:54 ` Namhyung Kim
2013-08-14 11:05 ` Adrian Hunter [this message]
2013-08-09 10:51 ` [PATCH V10 02/13] perf tools: allow non-matching sample types Adrian Hunter
2013-08-09 10:51 ` [PATCH V10 03/13] perf tools: add pid to struct thread Adrian Hunter
2013-08-09 10:51 ` [PATCH V10 04/13] perf tools: change machine__findnew_thread() to set thread pid Adrian Hunter
2013-08-13 3:01 ` Namhyung Kim
2013-08-09 10:51 ` [PATCH V10 05/13] perf tools: tidy up sample parsing overflow checking Adrian Hunter
2013-08-13 18:04 ` Jiri Olsa
2013-08-09 10:51 ` [PATCH V10 06/13] perf tools: remove unnecessary callchain validation Adrian Hunter
2013-08-13 3:33 ` Namhyung Kim
2013-08-09 10:51 ` [PATCH V10 07/13] perf tools: remove references to struct ip_event Adrian Hunter
2013-08-13 3:35 ` Namhyung Kim
2013-08-09 10:51 ` [PATCH V10 08/13] perf: make events stream always parsable Adrian Hunter
2013-08-09 10:51 ` [PATCH V10 09/13] perf tools: move perf_evlist__config() to a new source file Adrian Hunter
2013-08-13 3:39 ` Namhyung Kim
2013-08-09 10:51 ` [PATCH V10 10/13] perf tools: add support for PERF_SAMPLE_IDENTFIER Adrian Hunter
2013-08-09 10:51 ` [PATCH V10 11/13] perf tools: expand perf_event__synthesize_sample() Adrian Hunter
2013-08-13 18:18 ` Jiri Olsa
2013-08-09 10:51 ` [PATCH V10 12/13] perf tools: add a function to calculate sample event size Adrian Hunter
2013-08-13 18:22 ` Jiri Olsa
2013-08-09 10:51 ` [PATCH V10 13/13] perf tools: add a sample parsing test Adrian Hunter
2013-08-13 18:23 ` Jiri Olsa
2013-08-09 13:41 ` [PATCH V10 00/13] perf tools: some fixes and tweaks Stephane Eranian
2013-08-09 13:59 ` Adrian Hunter
2013-08-09 13:58 ` Stephane Eranian
2013-08-09 18:16 ` Adrian Hunter
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=520B6463.1010209@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/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