[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181016104722.GA18450@krava>
Date: Tue, 16 Oct 2018 12:47:22 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: John Garry <john.garry@...wei.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Andi Kleen <ak@...ux.intel.com>,
Mark Rutland <mark.rutland@....com>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will.deacon@....com>,
Linuxarm <linuxarm@...wei.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] perf tools: Store ids for events with their own cpus
perf_event__synthesize_event_update_cpus
On Tue, Oct 16, 2018 at 10:10:20AM +0100, John Garry wrote:
> On 15/10/2018 20:15, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Oct 12, 2018 at 02:25:49PM +0100, John Garry escreveu:
> > > On 09/10/2018 11:00, Jiri Olsa wrote:
> > > > On Thu, Oct 04, 2018 at 10:20:39AM +0100, John Garry wrote:
> > > >
> > > > SNIP
> > > >
> > > > > > We synthesize an update event that needs to touch the evsel
> > > > > > id array, which is not defined at that time. Fixing this by
> > > > > > forcing the id allocation for events with theeir own cpus.
> > >
> > > /s/theeir/their/
> > >
> > > > > >
> > > > > > Reported-by: John Garry <john.garry@...wei.com>
> > > > > > Link: http://lkml.kernel.org/n/tip-8x4n7o34yheigoxm1jibflm6@git.kernel.org
> > > > >
> > > > > Tested-by: John Garry <john.garry@...wei.com>
> > > > >
> > > > > In terms of adding to stable, LT v4.14 is not affected, but 4.18.x is.
> > > > >
> > > > > Thanks,
> > > > > John
> > > >
> > > > Arnaldo, could you please pick up this one
> > > >
> > >
> > > Just a friendly reminder on this patch.
> > >
> > > How about re-send with an updated commit message also?
> >
> > I'll fix up the commit message and apply, thanks.
> >
>
> Much appreciated.
>
> BTW, I think that we should add a fixes tag. But I'm not sure if this patch
> fixes the commit I bisected to earlier (bfd8f72c2778f5bd63d), or that same
> commit just exposed some latent bug.
>
> Jirka, Andi, Do you know?
yes, that commit moved it to record, which resulted in this fault
Arnaldo, could you please add:
Fixes: bfd8f72c2778 ("perf record: Synthesize unit/scale/... in event update")
thanks,
jirka
Powered by blists - more mailing lists