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]
Date:	Sun, 15 Jun 2014 22:03:09 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Hagen Paul Pfeifer <hagen@...u.net>
Cc:	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

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

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.
Maybe it can automatically download event file if it didn't find the
file in the local cache.


> 
> I also thought about further sub-command to delete the cache, update
> the cache, limit pull to specific vendors, ... I know this is the
> first shot and further subcommands can be added. But we will end up in
> something like
> E.g.:
> 
> perf events-download pull
> perf events-download pull --vendor amd
> perf events-download update
> perf events-download purge

Looks like 'event-cache' is a more appropriate name IMHO.

Anyway, thank you for the thought and suggestion. :)

Thanks,
Namhyung


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