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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140901191535.GF1900@krava.redhat.com>
Date:	Mon, 1 Sep 2014 21:15:35 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	Adrian Hunter <adrian.hunter@...el.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Namhyung Kim <namhyung@...il.com>,
	Paul Mackerras <paulus@...ba.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 20/41] perf tools: Let a user specify a PMU event without
 any config terms

On Mon, Sep 01, 2014 at 12:51:42PM -0300, Arnaldo Carvalho de Melo wrote:

SNIP

> >   krava alias: "tsc=1,noretcomp=0"
>  
> >   -e intel_pt/krava/
>  
> > which gives the same result
> 
> So you propose that we start maintaining some table of aliases that
> would be installed by default, etc? "krava" would not be a good name, I
> think (:-)), so in this case we would have something like:
> 
> 	defaults_intel_pt: "tsc=1,noretcomp=0"
> 
> 	-e intel_pt/defaults_intel_pt/
> 
> Which of course gets redundant/long, so, using what Adrian suggests, we
> would instead not pass anything between the slashes, and that would mean
> "default_" concatenated with the name of the PMU used, so it would
> become:
> 
> 	-e intel_pt//
> 
> that would be equivalent to:
> 
> 	-e intel_pt/defaults_intel_pt/
> 
> and also to:
> 
> 	-e intel_pt/tsc=1,noretcomp=0/
> 
> ?
> 
> I have not looked at the implementation, this is all just from the
> information I skimmed in this thread.

well I meant that we already have following directory:
  /sys/devices/cpu/events

for aliases.. files with format definitions (even partial)
I can imagine 'default' file there doing the same job
for the default format set

but I just could be missing something which is not apparent
from changelog ;-)

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