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: <20140716182214.GB32716@krava.redhat.com>
Date:	Wed, 16 Jul 2014 20:22:14 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	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 Wed, Jul 16, 2014 at 06:04:44PM +0300, Adrian Hunter wrote:
> On 16/07/2014 5:25 p.m., Jiri Olsa wrote:
> >On Mon, Jul 14, 2014 at 01:02:44PM +0300, Adrian Hunter wrote:
> >>This enables a PMU event to be specified in the form:
> >>
> >>	pmu//
> >>
> >>which is effectively the same as:
> >>
> >>	pmu/config=0/
> >>
> >>This patch is a precursor to defining
> >>default config for a PMU.
> >
> >I understand the need for default config, but could you please elaborate
> >why do we want to parse 'pmu//' as an event string string?
> 
> Currently the parser requires the slashes to identify a PMU event
> as opposed to a hardware or other kind of event.

right, so why do we want to parse 'pmu//' as an event string? ;-)

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