From: Andi Kleen <ak@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
mingo@redhat.com, Michael Ellerman <mpe@ellerman.id.au>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 4/4] perf: Create aliases for PMU events
Date: Mon, 4 May 2015 04:44:35 -0700 [thread overview]
Message-ID: <20150504114435.GQ13605@tassilo.jf.intel.com> (raw)
In-Reply-To: <20150502153814.GA21242@krava.redhat.com>
> I personaly like having set of event files in JSON notation
> rather than having them directly in C structure
Yes, strings are better and JSON input is also better.
I prototyped translating JSON into the proposed structures. I already had to
add three new fields, and it wouldn't work for uncore. The string
format is much more extensible.
BTW as expected the binary sizes are gigantic (for 14 CPU types):
% size all.o
text data bss dec hex filename
662698 0 0 662698 a1caa all.o
% gcc -E all.c | wc -l
55475
-Andi
next prev parent reply other threads:[~2015-05-04 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 7:05 [RFC][PATCH 0/4] perf: Enable symbolic event names Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 1/4] perf: Create a table of Power7 PMU events Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 2/4] perf: Create a table of Power8 " Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 3/4] perf/powerpc: Move mfspr and friends to header file Sukadev Bhattiprolu
2015-05-01 7:05 ` [RFC][PATCH 4/4] perf: Create aliases for PMU events Sukadev Bhattiprolu
2015-05-02 7:04 ` Vineet Gupta
2015-05-02 15:38 ` Jiri Olsa
2015-05-04 11:44 ` Andi Kleen [this message]
2015-05-02 7:02 ` [RFC][PATCH 0/4] perf: Enable symbolic event names Vineet Gupta
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=20150504114435.GQ13605@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sukadev@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).