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 V9 01/14] perf tools: add debug prints
Date: Wed, 07 Aug 2013 11:13:23 +0300 [thread overview]
Message-ID: <520201A3.4030606@intel.com> (raw)
In-Reply-To: <8738qmyp7i.fsf@sejong.aot.lge.com>
On 07/08/13 09:44, Namhyung Kim wrote:
> Hi Adrian,
>
> On Mon, 5 Aug 2013 19:26:21 +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
>>
> [SNIP]
>>
>> +static size_t perf_event_attr__fprintf(struct perf_event_attr *attr, FILE *fp)
>> +{
>> + size_t ret;
>> +
>> + ret = fprintf(fp, "------------------------------------------------------------\n");
>> + ret += fprintf(fp, "perf_event_attr:\n");
>> + ret += fprintf(fp, " type %u\n", attr->type);
>> + ret += fprintf(fp, " size %u\n", attr->size);
>> + ret += fprintf(fp, " config %#"PRIx64"\n", (uint64_t)attr->config);
>> + ret += fprintf(fp, " sample_period %"PRIu64"\n", (uint64_t)attr->sample_period);
>> + ret += fprintf(fp, " sample_freq %"PRIu64"\n", (uint64_t)attr->sample_freq);
>> + ret += fprintf(fp, " sample_type %#"PRIx64"\n", (uint64_t)attr->sample_type);
>> + ret += fprintf(fp, " read_format %#"PRIx64"\n", (uint64_t)attr->read_format);
>> +
>> + ret += fprintf(fp, " disabled %u ", attr->disabled);
>> + ret += fprintf(fp, "inherit %u\n", attr->inherit);
>> + ret += fprintf(fp, " pinned %u ", attr->pinned);
>> + ret += fprintf(fp, "exclusive %u\n", attr->exclusive);
>> + ret += fprintf(fp, " exclude_user %u ", attr->exclude_user);
>> + ret += fprintf(fp, "exclude_kernel %u\n", attr->exclude_kernel);
>> + ret += fprintf(fp, " exclude_hv %u ", attr->exclude_hv);
>> + ret += fprintf(fp, "exclude_idle %u\n", attr->exclude_idle);
>> + ret += fprintf(fp, " mmap %u ", attr->mmap);
>> + ret += fprintf(fp, "comm %u\n", attr->comm);
>> + ret += fprintf(fp, " freq %u ", attr->freq);
>> + ret += fprintf(fp, "inherit_stat %u\n", attr->inherit_stat);
>> + ret += fprintf(fp, " enable_on_exec %u ", attr->enable_on_exec);
>> + ret += fprintf(fp, "task %u\n", attr->task);
>> + ret += fprintf(fp, " watermark %u ", attr->watermark);
>> + ret += fprintf(fp, "precise_ip %u\n", attr->precise_ip);
>> + ret += fprintf(fp, " mmap_data %u ", attr->mmap_data);
>> + ret += fprintf(fp, "sample_id_all %u\n", attr->sample_id_all);
>> + ret += fprintf(fp, " exclude_host %u ", attr->exclude_host);
>> + ret += fprintf(fp, "exclude_guest %u\n", attr->exclude_guest);
>> + ret += fprintf(fp, " excl.callchain.kern %u ", attr->exclude_callchain_kernel);
>> + ret += fprintf(fp, "excl.callchain.user %u\n", attr->exclude_callchain_user);
>> +
>> + ret += fprintf(fp, " wakeup_events %u\n", attr->wakeup_events);
>> + ret += fprintf(fp, " wakeup_watermark %u\n", attr->wakeup_watermark);
>> + ret += fprintf(fp, " bp_type %#x\n", attr->bp_type);
>> + ret += fprintf(fp, " bp_addr %#"PRIx64"\n", (uint64_t)attr->bp_addr);
>> + ret += fprintf(fp, " config1 %#"PRIx64"\n", (uint64_t)attr->config1);
>> + ret += fprintf(fp, " bp_len %"PRIu64"\n", (uint64_t)attr->bp_len);
>> + ret += fprintf(fp, " config2 %#"PRIx64"\n", (uint64_t)attr->config2);
>> + ret += fprintf(fp, " branch_sample_type %#"PRIx64"\n", (uint64_t)attr->branch_sample_type);
>> + ret += fprintf(fp, " sample_regs_user %#"PRIx64"\n", (uint64_t)attr->sample_regs_user);
>> + ret += fprintf(fp, " sample_stack_user %u\n", attr->sample_stack_user);
>
> Things like this likely being ended up with typo. How about this? (not tested)
And yet there aren't any typos.
>
> #define __PRINT_ATTR(fmt, cast, field) \
> fprintf(fp, " %-28s "fmt"\n", #field, cast attr->field)
>
> #define PRINT_ATTR_D32(field) __PRINT_ATTR("%u", ,field)
> #define PRINT_ATTR_X32(field) __PRINT_ATTR("%#x", ,field)
> #define PRINT_ATTR_D64(field) __PRINT_ATTR("%"PRIu64, (uint64_t), field)
> #define PRINT_ATTR_X64(field) __PRINT_ATTR("%#"PRIx64, (uint64_t), field)
> #define PRINT_ATTR2(field1, field2) \
> fprintf(fp, " %-28s %u %-28s %u\n", \
> #field1, attr->field1, #field2, attr->field2)
That does not allow the output to be nicely formatted. In some cases the
field name is just too long and I have abbreviated it.
When you add in all the variations you just get a macro mess.
>
> Thanks,
> Namhyung
>
>
>> + ret += fprintf(fp, "------------------------------------------------------------\n");
>> +
>> + return ret;
>> +}
>
>
next prev parent reply other threads:[~2013-08-07 8:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 16:26 [PATCH V9 00/14] perf tools: some fixes and tweaks Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 01/14] perf tools: add debug prints Adrian Hunter
2013-08-07 6:44 ` Namhyung Kim
2013-08-07 8:13 ` Adrian Hunter [this message]
2013-08-07 8:50 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 02/14] perf tools: allow non-matching sample types Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 03/14] perf tools: add pid to struct thread Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 04/14] perf tools: change machine__findnew_thread() to set thread pid Adrian Hunter
2013-08-07 7:51 ` Namhyung Kim
2013-08-07 8:34 ` Adrian Hunter
2013-08-07 8:40 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 05/14] perf tools: tidy up sample parsing overflow checking Adrian Hunter
2013-08-07 8:09 ` Namhyung Kim
2013-08-07 8:19 ` Adrian Hunter
2013-08-07 8:54 ` Namhyung Kim
2013-08-07 11:45 ` Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 06/14] perf tools: remove unnecessary callchain validation Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 07/14] perf tools: remove references to struct ip_event Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 08/14] perf tools: move " Adrian Hunter
2013-08-07 8:22 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 09/14] perf: make events stream always parsable Adrian Hunter
2013-08-12 8:52 ` Peter Zijlstra
2013-08-05 16:26 ` [PATCH V9 10/14] perf tools: move perf_evlist__config() to a new source file Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 11/14] perf tools: add support for PERF_SAMPLE_IDENTFIER Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 12/14] perf tools: expand perf_event__synthesize_sample() Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 13/14] perf tools: add a function to calculate sample event size Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 14/14] perf tools: add a sample parsing test 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=520201A3.4030606@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 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.