[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120625232016.GA28525@infradead.org>
Date: Mon, 25 Jun 2012 20:20:16 -0300
From: Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To: Dmitry Antipov <dmitry.antipov@...aro.org>
Cc: Namhyung Kim <namhyung@...nel.org>, Ingo Molnar <mingo@...hat.com>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
patches@...aro.org
Subject: Re: [PATCH] perf sched replay: fix event lookup
Em Tue, Jun 12, 2012 at 03:01:26PM +0900, Namhyung Kim escreveu:
> On Mon, 11 Jun 2012 11:08:52 -0300, Arnaldo Carvalho de Melo wrote:
> > So I think we should have a per perf.data (perf_session) method that
> > knows that it shouldn't look _at all_ to /sys, but just at what came in
> > the perf.data file.
> >
>
> Fair enough. The method should be a simple wrapper to libtraceevent APIs
> like this patch.
The pevent thing is per perf.data file, so I made it stop being static
and become a perf_session member, so tools processing perf.data files
use perf_session and _there_ we read the event into session->pevent and
then have to change everywhere to stop using that single global pevent
variable and use the per session one.
Dmitry, can you test the attached patch to check if it solves the
problems you reported?
Note that it _doesn't_ fall backs to trace__event_id, as we're not
interested at all in what is present in the
/sys/kernel/debug/tracing/events in the workstation doing the analysis,
just in what is in the perf.data file.
- Arnaldo
View attachment "per_session_pevent.patch" of type "text/plain" (41582 bytes)
Powered by blists - more mailing lists