On Thu, Jun 11, 2015 at 10:07:40PM +0900, Namhyung Kim wrote: > 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?
I guess thats possiuble, but we already have it for cpu map in evsel, so I wanted to stay consistent with thread map.. and it's just pointer with extra refcnt increased jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
