Re: [PATCH 01/21] perf c2c: Shared data analyser

[Arnaldo Carvalho de Melo]

Em Mon, Feb 10, 2014 at 02:10:04PM -0800, Davidlohr Bueso escreveu:
> On Mon, 2014-02-10 at 14:18 -0500, Don Zickus wrote:
> > From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
> > 
> > This is the start of a new perf tool that will collect information about
> > memory accesses and analyse it to find things like hot cachelines, etc.
> > 
> > This is basically trying to get a prototype written by Richard Fowles
> > written using the tools/perf coding style and libraries.
> > 
> > Start it from 'perf sched', this patch starts the process by adding the
> > 'record' subcommand to collect the needed mem loads and stores samples.
> > 
> > It also have the basic 'report' skeleton, resolving the sample address
> > and hooking the events found in a perf.data file with methods to handle
> > them, right now just printing the resolved perf_sample data structure
> > after each event name.
> 
> What tree/branch is this developed against? I'm getting the following
> with Linus' latest and tip tree:

I'll try refreshing it on top of my perf/core branch today
 
> builtin-c2c.c: In function âperf_c2c__process_sampleâ:
> builtin-c2c.c:68:20: error: request for member âfuncâ in something not a structure or union
> builtin-c2c.c:69:36: error: request for member âfuncâ in something not a structure or union
> builtin-c2c.c: In function âperf_c2c__read_eventsâ:
> builtin-c2c.c:81:2: error: passing argument 1 of âperf_session__newâ from incompatible pointer type [-Werror]
> In file included from builtin-c2c.c:6:0:
> util/session.h:52:22: note: expected âstruct perf_data_file *â but argument is of type âconst char *â
> builtin-c2c.c:81:2: error: too many arguments to function âperf_session__newâ
> In file included from builtin-c2c.c:6:0:
> util/session.h:52:22: note: declared here
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/