From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Tom Huynh <tom.huynh@freescale.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, acme@kernel.org,
Andi Kleen <andi@firstfloor.org>,
paulus@samba.org, Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org, mingo@redhat.com
Subject: Re: [PATCH 1/3] perf/e6500: Make event translations available in sysfs
Date: Wed, 18 Feb 2015 22:31:34 +0100 [thread overview]
Message-ID: <20150218213134.GA823@two.firstfloor.org> (raw)
In-Reply-To: <20150218205603.GA21074@gmail.com>
Well I'm tired of discussing this. I don't think what you
proposed makes sense, putting 3.4MB[1] of changing blob into perf.
I'll resubmit the JSON parser without the downloader. Then users
have the option to get their own events and use that.
If you don't like that, standard perf just has to stay with limited
events and rXXXX as before, with users having to use external
tools or libraries for names for more events[2][3].
-Andi
[1] Current size of https://download.01.org/perfmon/
[2] ocperf in https://github.com/andikleen/pmu-tools
[3] http://perfmon2.sourceforge.net/
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2015-02-18 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 22:43 [PATCH 0/3] Add e6500 perf events to sysfs and update perf doc Tom Huynh
2015-02-06 22:43 ` [PATCH 1/3] perf/e6500: Make event translations available in sysfs Tom Huynh
2015-02-09 10:02 ` Peter Zijlstra
2015-02-09 10:07 ` Ingo Molnar
2015-02-09 12:11 ` Jiri Olsa
2015-02-09 13:25 ` Ingo Molnar
2015-02-09 20:40 ` Andi Kleen
2015-02-11 0:19 ` Scott Wood
2015-02-18 20:56 ` Ingo Molnar
2015-02-18 21:31 ` Andi Kleen [this message]
2015-02-16 16:10 ` Tom Huynh
2015-03-27 21:34 ` Kim Phillips
2015-03-28 0:32 ` Andi Kleen
2015-02-06 22:43 ` [PATCH 2/3] perf/e6500: Create a sysfs format entry for e6500 events Tom Huynh
2015-02-06 22:43 ` [PATCH 3/3] perf/doc: Update perf_event_attr struct Tom Huynh
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=20150218213134.GA823@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=scottwood@freescale.com \
--cc=tom.huynh@freescale.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).