We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Note: This was originally posted on 6th September 2013 at forums.arm.com
I am glad that this problem is fixed. To help fix the problem for future users, will you please answer a followup question - when I remove CONFIG_HW_PERF_EVENT from my config I get this error> make -C ~/linux-linaro-tracking M=`pwd` ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- modulesmake: Entering directory `~/linux-linaro-tracking'CHK gator_events.hCC [M] ~/gator/driver/gator_main.o~/gator/driver/gator_main.c:55:2: error: #error gator requires the kernel to have CONFIG_HW_PERF_EVENTS defined to support pmu hardware countersmake[1]: *** [~/gator/driver/gator_main.o] Error 1make: *** [_module_/~/gator/driver] Error 2make: Leaving directory `~/linux-linaro-tracking'The lines that create the error are as follows in the gator sources distributed with DS5 v5.15:driver/gator.h:18:#define GATOR_PERF_PMU_SUPPORT GATOR_PERF_SUPPORT && defined(CONFIG_PERF_EVENTS) && (!(defined(__arm__) || defined(__aarch64__)) || defined(CONFIG_HW_PERF_EVENTS))driver/gator_main.c:51:#if (GATOR_PERF_SUPPORT) && (!(GATOR_PERF_PMU_SUPPORT))driver/gator_main.c:52:#ifndef CONFIG_PERF_EVENTSdriver/gator_main.c:53:#error gator requires the kernel to have CONFIG_PERF_EVENTS defined to support pmu hardware countersdriver/gator_main.c:54:#elif !defined CONFIG_HW_PERF_EVENTSdriver/gator_main.c:55:#error gator requires the kernel to have CONFIG_HW_PERF_EVENTS defined to support pmu hardware countersdriver/gator_main.c:56:#endifdriver/gator_main.c:57:#endifWhat does your gator.ko source code look like?
Hi Drew,
If I compile gator.ko without enabling CONFIG_HW_PERF_EVENTS, I will got errors too. What I did before was to enable it in menuconfig, then compile gator.ko. However, this was done after I have built the kernel. As you have said before, the kernel image running on my device does not get CONFIG_HW_PERF_EVENTS enabled in this way.
But I am still not sure how I solved this unknown symbol problem.
Thank you!
Best regards,
Xiaowan