New: Oprofile runtime issue

https://bugs.busybox.net/show_bug.cgi?id=12146

Bug ID: 12146
Summary: Oprofile runtime issue
Product: buildroot
Version: 2019.02.4
Hardware: All
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ragaprasanth at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Created attachment 8221
--> https://bugs.busybox.net/attachment.cgi?id=8221&action=edit
defconfig used for Beaglebone Black + oprofile

Hi,

I tried building oprofile for my Beagle bone Black (cortex-A8), where the build went fine. But, I could see a runtime issue.

Could any help me with this?

Attached defconfig and pasted the error-log at runtime.

# operf --version
Unexpected error running operf: Operation not supported
#

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12146

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Thanks for your bug report. This seems like a kernel configuration issue. Did you had CONFIG_OPROFILE=y in your kernel configuration?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=12146

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Thomas Petazzoni <[email protected]> --- Looked at it in more details, if you get EOPNOTSUPP, then you probably do have CONFIG_OPROFILE=y enabled, but the perf_event_open() syscall fails and returns EOPNOTSUPP. One reason for this to happen is when:

        if (is_sampling_event(event)) {
                if (event->pmu->capabilities & PERF_PMU_CAP_NO_INTERRUPT) {
                        err = -EOPNOTSUPP;
                        goto err_alloc;
                }
        }

So this really depends on your hardware PMU, and the kernel support for it. This is not a Buildroot bug.

You are receiving this mail because:
You are on the CC list for the bug.