From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12146] Oprofile runtime issue
Date: Fri, 29 Nov 2019 13:07:41 +0000 [thread overview]
Message-ID: <bug-12146-163-0j8MuH717f@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12146-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12146
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
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.
prev parent reply other threads:[~2019-11-29 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 11:11 [Buildroot] [Bug 12146] New: Oprofile runtime issue bugzilla at busybox.net
2019-11-29 7:35 ` [Buildroot] [Bug 12146] " bugzilla at busybox.net
2019-11-29 13:07 ` bugzilla at busybox.net [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12146-163-0j8MuH717f@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.