linux-kernel - Re: [PATCH 06/25] perf tools: Propagate thread maps through the evlist

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: <20150611130740.GA31117@danjae.kornet>
Date:	Thu, 11 Jun 2015 22:07:40 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Jiri Olsa <jolsa@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Andi Kleen <ak@...ux.intel.com>,
	David Ahern <dsahern@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 06/25] perf tools: Propagate thread maps through the
 evlist

Hi Jiri,

On Wed, Jun 10, 2015 at 10:25:13PM +0200, Jiri Olsa wrote:
> On Wed, Jun 10, 2015 at 04:09:32PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Jun 10, 2015 at 08:10:39PM +0200, Jiri Olsa escreveu:
> > > Propagate evlist's thread_map object through all the
> > > evsel objects.
> > > 
> > > It'll be handy to access evsel's threads directly
> > > in following patches.
> > 
> > Handy in what way? I.e. I should know one example without having to look
> > at future patches ;-)
> 
> there's no link to evlist which hold threads map now,
> and it's not always available.. I'll update the changelog
> in v2

What about adding a link to evlist in evsel then?

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/