Re: Clarification on support of arm32 with kernel4.1 for oprofile 1.2.0
Vinoth Natarajan <[email protected]>
| Newsgroups | gmane.linux.oprofile |
|---|---|
| Message-ID | <CADaxUdGqRWThiCaBNme9pMD0KFdcw7mU9VePXPMigR39y7yjYA@mail.gmail.com> |
Hello Michael, Thanks so much for the help. Cross compiled the hello.c with crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22 and tested the executable on the target(arm32) Received the following error " ./hello Error opening leader 1" Following are the kernel configs related to PERF in target cat /tmp/test |grep PERF CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y CONFIG_PERF_EVENTS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_HAVE_PERF_REGS=y CONFIG_HAVE_PERF_USER_STACK_DUMP=y # CONFIG_PCIEASPM_PERFORMANCE is not set # CONFIG_HW_PERF_EVENTS is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set # CONFIG_CLS_U32_PERF is not set Could you please share your feedback on this. Thanks in Advance!!! Thanks and Regards, Vinoth Natarajan. On Wed, Feb 14, 2018 at 11:01 PM, Michael Petlan <[email protected]> wrote: > On Tue, 13 Feb 2018, Vinoth Natarajan wrote: > > Hello Team, > > Good Day!!! > > > > Cross Compiled the oprofile-1.2.0 in ubuntu. > > Hi, it's nice to see that you finally managed to compile it. > > [...] > > > > once compiled,tested the oprofile binaries in target (arm32 hw running > on kernel-4.1) > > Received the following error > > > > # operf > > Your kernel does not implement a required syscall for the operf program. > > > > While checking found that CONFIG_PERF_EVENTS is not set, So enabled the > same and tested the orpfile resulted the following error. > > > > > > # operf --help > > Your kernel's Performance Events Subsystem does not support your > processor type. > > > > > > if i change the oprofile-1.2.0 with oprofile 0.9.9 it works fine > (oprofile running in legacy mode) > > > > Can anyone let me understand why oprofile-1.2.0 give " Your kernel's > Performance Events Subsystem does not support your processor type. " error. > > I would first try to figure out whether the kernel subsystem works or not. > Try to compile the attached hello.c and run it there. You need kernel-devel > and headers. > > $ cc -o hello hello.c > $ ./hello > Measuring instruction count for this printf > Used 3259 instructions > > Does this work for you? > If yes, it's oprofile who has a problem, but it is pretty probable, that > the problem lies in kernel backend. > > Cheers, > Michael > > > > > Is arm32 not supported in oprofile-1.2.0 with kernel -4.1? > > > > Please explain this !!! > > > > Thanks in Advance.. > > > > Thanks and Regards, > > Vinoth Natarajan. > > > > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ oprofile-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oprofile-list