[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170918113044.GA7518@krava>
Date: Mon, 18 Sep 2017 13:30:44 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: "Liang, Kan" <kan.liang@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"Hunter, Adrian" <adrian.hunter@...el.com>,
"Odzioba, Lukasz" <lukasz.odzioba@...el.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: Re: [PATCH RFC V2 07/10] perf tools: change machine comm_exec type
to atomic
On Fri, Sep 15, 2017 at 08:05:11PM +0000, Liang, Kan wrote:
> > Em Sun, Sep 10, 2017 at 07:23:20PM -0700, kan.liang@...el.com escreveu:
> > > From: Kan Liang <kan.liang@...el.com>
> > >
> > > In case there are two or more threads want to change it.
> >
> > Please describe the scenario that made you want to have this in place, to
> > help in reviewing and to have it documented in this patch commit log.
> >
>
> Thinking more about it. For synthesizing event, we don't need to change the
> comm_exec. PERF_RECORD_MISC_COMM_EXEC is not set in this stage.
> But we should consider it if we want to multithread the event processing stage.
>
> Since it's not an issue for now, I will drop this patch and add some comments
> in the code for V3.
any chance you could push v3 into a git branch somewhere?
thanks,
jirka
Powered by blists - more mailing lists