Re: [tip:perf/core] perf events, x86: Add SandyBridgestalled-cycles-frontend/backend events

From: Ingo Molnar
Date: Fri May 06 2011 - 15:08:48 EST



* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> On Fri, 2011-05-06 at 07:40 +0000, tip-bot for Lin Ming wrote:
> > Commit-ID: e04d1b23f9706186187dcb0be1a752e48dcc540b
> > Gitweb: http://git.kernel.org/tip/e04d1b23f9706186187dcb0be1a752e48dcc540b
> > Author: Lin Ming <ming.m.lin@xxxxxxxxx>
> > AuthorDate: Fri, 6 May 2011 07:14:02 +0000
> > Committer: Ingo Molnar <mingo@xxxxxxx>
> > CommitDate: Fri, 6 May 2011 09:37:03 +0200
> >
> > perf events, x86: Add SandyBridge stalled-cycles-frontend/backend events
> >
> > Extend the Intel SandyBridge PMU driver with definitions
> > for generic front-end and back-end stall events.
> >
> > ( As commit 3011203 "perf events, x86: Add Westmere stalled-cycles-frontend/backend
> > events" says, these are only approximations. )
>
> I now get the following build error:
>
> In file included from /home/rostedt/work/autotest/nobackup/linux-test.git/arch/x86/kernel/cpu/perf_event.c:1449:0:
> /home/rostedt/work/autotest/nobackup/linux-test.git/arch/x86/kernel/cpu/perf_event_intel.c: In function 'intel_pmu_init':
> /home/rostedt/work/autotest/nobackup/linux-test.git/arch/x86/kernel/cpu/perf_event_intel.c:1479:27: error: 'PERF_COUNT_HW_STALLED_CYCLES_FRONTEND' undeclared (first use in this fun
> ction)
> /home/rostedt/work/autotest/nobackup/linux-test.git/arch/x86/kernel/cpu/perf_event_intel.c:1479:27: note: each undeclared identifier is reported only once for each function it appe
> ars in
> /home/rostedt/work/autotest/nobackup/linux-test.git/arch/x86/kernel/cpu/perf_event_intel.c:1481:27: error: 'PERF_COUNT_HW_STALLED_CYCLES_BACKEND' undeclared (first use in this func
> tion)
>
> Config can be found here:
>
> http://rostedt.homelinux.com/private/config-sandy-failed

Ok, could you check latest perf/core (57d524154ffe), does it work better?

Thanks,

Ingo
--
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/