From: Andi Kleen <andi@firstfloor.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>,
Andi Kleen <andi@firstfloor.org>,
jolsa@redhat.com, linux-kernel@vger.kernel.org,
acme@infradead.org
Subject: Re: perf: Add support for full Intel event lists v6
Date: Sun, 15 Jun 2014 18:09:25 +0200 [thread overview]
Message-ID: <20140615160925.GG5714@two.firstfloor.org> (raw)
In-Reply-To: <1402837389.1684.25.camel@leonhard>
On Sun, Jun 15, 2014 at 10:03:09PM +0900, Namhyung Kim wrote:
> Hi Hagen,
>
> 2014-06-14 (토), 22:49 +0200, Hagen Paul Pfeifer:
> > Probably too late, but IMHO the subcommand "download" is unhappy
> > named. What is "downloaded"? traces? Python helper libs for
> > perf-python support, I don't know it. What about "events-download",
> > "events-database", ...
>
> Hmm.. maybe we can add support something like above later - "perf
> download event" or "perf download blabla"
Sorry I think that's all overdesigning. Designing for unknown
possibilities is usually a bad idea.
In the unlikely case that something else was ever downloaded a new command
can be added.
> But I have a different idea - leaving perf download as a plumbing tool,
> and add --download option into the perf list to call it internally.
That would be syntactical vinegar.
> Maybe it can automatically download event file if it didn't find the
> file in the local cache.
That wasn't done intentionally, so that people who don't want
network accesses don't get them.
-Andi
next prev parent reply other threads:[~2014-06-15 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 23:02 Andi Kleen
2014-06-13 23:02 ` [PATCH 1/9] perf, tools: Add jsmn `jasmine' JSON parser v3 Andi Kleen
2014-06-13 23:02 ` [PATCH 2/9] perf, tools: Add support for text descriptions of events and alias add Andi Kleen
2014-06-13 23:02 ` [PATCH 3/9] perf, tools: Add support for reading JSON event files v3 Andi Kleen
2014-06-13 23:02 ` [PATCH 4/9] perf, tools: Automatically look for event file name for cpu v3 Andi Kleen
2014-07-09 2:13 ` Sukadev Bhattiprolu
2014-07-09 4:07 ` Andi Kleen
2014-06-13 23:02 ` [PATCH 5/9] perf, tools: Add perf download to download event files v4 Andi Kleen
2014-06-13 23:02 ` [PATCH 6/9] perf, tools: Allow events with dot Andi Kleen
2014-06-13 23:02 ` [PATCH 7/9] perf, tools: Query terminal width and use in perf list Andi Kleen
2014-06-13 23:02 ` [PATCH 8/9] perf, tools, test: Add test case for alias and JSON parsing v2 Andi Kleen
2014-06-13 23:03 ` [PATCH 9/9] perf, tools: Add a --quiet flag to perf list Andi Kleen
2014-06-15 13:17 ` Namhyung Kim
2014-06-15 16:11 ` Andi Kleen
2014-06-18 0:36 ` Namhyung Kim
2014-07-09 22:20 ` Jiri Olsa
2014-06-14 20:49 ` perf: Add support for full Intel event lists v6 Hagen Paul Pfeifer
2014-06-14 21:28 ` Andi Kleen
2014-06-15 13:03 ` Namhyung Kim
2014-06-15 16:09 ` Andi Kleen [this message]
2014-06-16 8:20 ` Hagen Paul Pfeifer
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=20140615160925.GG5714@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=hagen@jauu.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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
Powered by JetHome