lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140615160925.GG5714@two.firstfloor.org>
Date:	Sun, 15 Jun 2014 18:09:25 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Hagen Paul Pfeifer <hagen@...u.net>,
	Andi Kleen <andi@...stfloor.org>, jolsa@...hat.com,
	linux-kernel@...r.kernel.org, acme@...radead.org
Subject: Re: perf: Add support for full Intel event lists v6

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
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ