[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140515191231.GC1873@two.firstfloor.org>
Date: Thu, 15 May 2014 21:12:31 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Hagen Paul Pfeifer <hagen@...u.net>
Cc: Andi Kleen <andi@...stfloor.org>, acme@...radead.org,
linux-kernel@...r.kernel.org, peterz@...radead.org,
eranian@...gle.com, namhyung@...nel.org, jolsa@...hat.com
Subject: Re: perf: Add support for full Intel event lists v3
On Thu, May 15, 2014 at 06:09:20PM +0200, Hagen Paul Pfeifer wrote:
> On 13 May 2014 00:51, Andi Kleen <andi@...stfloor.org> wrote:
>
> > I implemented an automatic downloader to get the event file for the
> > current CPU. The events are stored in ~/.events.
> > Then perf adds a parser that converts the JSON format into perf event
> > aliases, which then can be used directly as any other perf event.
>
> Should the name of the file not more specific? I mean .events can mean
> everything? Every program may have a demand for this generic name. Why
> not ~/.perf-events? Even more standard [1]:
> $XDG_CACHE_HOME/perf/events (i.e. ~/.cache/perf/events)
It's already pmu-events, but I forgot to update the description.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists