From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752720AbbFLUOO (ORCPT <rfc822;w@1wt.eu>);
	Fri, 12 Jun 2015 16:14:14 -0400
Received: from mx1.redhat.com ([209.132.183.28]:39307 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751242AbbFLUOJ (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 12 Jun 2015 16:14:09 -0400
Date: Fri, 12 Jun 2015 22:13:59 +0200
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
        lkml <linux-kernel@vger.kernel.org>,
        Adrian Hunter <adrian.hunter@intel.com>,
        Andi Kleen <ak@linux.intel.com>, David Ahern <dsahern@gmail.com>,
        Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 06/25] perf tools: Propagate thread maps through the
 evlist
Message-ID: <20150612201359.GB25788@krava.redhat.com>
References: <1433959858-31858-1-git-send-email-jolsa@kernel.org>
 <1433959858-31858-7-git-send-email-jolsa@kernel.org>
 <20150610190932.GG3332@kernel.org>
 <20150610202513.GG6803@krava.redhat.com>
 <20150611130740.GA31117@danjae.kornet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150611130740.GA31117@danjae.kornet>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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