From: Andi Kleen <andi@firstfloor.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
eranian@google.com, namhyung@kernel.org, jolsa@redhat.com
Subject: Re: perf: Add support for full Intel event lists
Date: Mon, 10 Mar 2014 23:14:20 +0100 [thread overview]
Message-ID: <20140310221420.GM22728@two.firstfloor.org> (raw)
In-Reply-To: <1394480354.23624.7.camel@deadeye.wl.decadent.org.uk>
On Mon, Mar 10, 2014 at 07:39:14PM +0000, Ben Hutchings wrote:
> On Wed, 2014-03-05 at 11:49 -0800, Andi Kleen wrote:
> [...]
> > I implemented an automatic downloader to get the event file for the
> > current CPU. The events are stored in ~/.events.
> [...]
>
> This directory should be placed under $XDG_CACHE_DIR (default:
> ~/.cache), and should have a more specific name like 'perf-events'.
Ok.
I don't like calling it perf-events because it will be used
by other non perf tools too. I guess pmu-events could do.
>
> It might be useful to also support a system directory for these,
> under /var/cache.
I don't want people shipping those. It just causes lots
of outdated events everywhere, like in oprofile.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2014-03-10 22:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 19:49 perf: Add support for full Intel event lists Andi Kleen
2014-03-05 19:49 ` [PATCH 1/8] perf, tools: Add jsmn `jasmine' JSON parser Andi Kleen
2014-03-11 10:23 ` Jiri Olsa
2014-03-11 13:37 ` Jiri Olsa
2014-03-11 13:38 ` Jiri Olsa
2014-03-13 20:06 ` Andi Kleen
2014-03-11 13:38 ` Jiri Olsa
2014-03-13 20:07 ` Andi Kleen
2014-03-11 13:38 ` Jiri Olsa
2014-03-05 19:49 ` [PATCH 2/8] perf, tools: Add support for reading JSON event files Andi Kleen
2014-03-11 13:37 ` Jiri Olsa
2014-03-05 19:49 ` [PATCH 3/8] perf, tools: Automatically look for event file name for cpu Andi Kleen
2014-03-11 13:37 ` Jiri Olsa
2014-03-05 19:49 ` [PATCH 4/8] perf, tools: Add perf download to download event files Andi Kleen
2014-03-05 19:49 ` [PATCH 5/8] perf, tools: Allow events with dot Andi Kleen
2014-03-05 19:49 ` [PATCH 6/8] perf, tools: Query terminal width and use in perf list Andi Kleen
2014-03-11 13:41 ` Jiri Olsa
2014-03-05 19:49 ` [PATCH 7/8] perf, tools, record: Always allow to overide default period Andi Kleen
2014-03-11 14:26 ` Jiri Olsa
2014-03-05 19:49 ` [PATCH 8/8] perf, tools, test: Add test case for alias and JSON parsing Andi Kleen
2014-03-11 14:31 ` Jiri Olsa
2014-03-14 21:12 ` Andi Kleen
2014-03-06 9:37 ` perf: Add support for full Intel event lists Jiri Olsa
2014-03-10 19:39 ` Ben Hutchings
2014-03-10 22:14 ` Andi Kleen [this message]
2014-03-10 23:13 ` Ben Hutchings
2014-03-10 23:31 ` Andi Kleen
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=20140310221420.GM22728@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=ben@decadent.org.uk \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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