Re: Implement lbr-as-callgraph v10

From: Jiri Olsa
Date: Tue Nov 18 2014 - 05:44:39 EST

On Mon, Nov 17, 2014 at 06:34:57PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 12, 2014 at 06:05:18PM -0800, Andi Kleen escreveu:
> > [Reworks to address all the review feedback. Rebased to latest tree]
> > [Just a repost after a rebase]
> > [Even more review feedback and some bugs addressed.]
> > [Only port to changes in perf/core. No other changes.]
> > [Rebase to latest perf/core]
> > [Another rebase. No changes]
> >
> > This patchkit implements lbr-as-callgraphs in per freport,
> > as an alternative way to present LBR information.
> Ok, I have this in my perf/core branch, but I need to test it further,
> as I couldn't get the output that appears on some of the changelogs.
> If you could take a look at
> git:// perf/core
> To see if I made some mistake, that would be of help,

I'm getting compile error for DEBUG=1


[jolsa@krava perf]$ make DEBUG=1 JOBS=1
BUILD: Doing 'make -j1' parallel build
CC util/machine.o
In file included from /home/jolsa/,
from /home/jolsa/,
from /home/jolsa/,
from util/../perf.h:7,
from util/callchain.h:4,
from util/machine.c:1:
util/machine.c: In function âremove_loopsâ:
/home/jolsa/ error: call to â__compiletime_assert_1450â declared with attribute error: Please upgrade the type of the hash table from unsigned char
prefix ## suffix(); \
/home/jolsa/ note: in expansion of macro â__compiletime_assertâ
__compiletime_assert(condition, msg, prefix, suffix)
/home/jolsa/ note: in expansion of macro â_compiletime_assertâ
_compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
/home/jolsa/ note: in expansion of macro âcompiletime_assertâ
#define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
util/machine.c:1449:2: note: in expansion of macro âBUILD_BUG_ON_MSGâ
make[1]: *** [util/machine.o] Error 1
make: *** [all] Error 2
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at