From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14641] New: oprofile can not find the events files
Date: Mon, 07 Mar 2022 10:08:10 +0000 [thread overview]
Message-ID: <bug-14641-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14641
Bug ID: 14641
Summary: oprofile can not find the events files
Product: buildroot
Version: 2020.02.12
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: sergey.velykokhatko@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hi all,
We are using Intel ApolloLake AtomE3930 SOC with goldmont microarchitecture.
Buildroot configure file contains the BR2_x86_64=y. When we starting the operf,
we get following error:
oprofile: could not open unit mask description file
/usr/share/oprofile//i386/goldmont/unit_masks
Unable to find info for event cpu_clk_unhalted
It looks for me a problem in OPROFILE_INSTALL_TARGET_CMDS. It copies the x86-64
for our SOC, but oprofile awaits them at i386 Architecture, s.
https://docs.fedoraproject.org/en-US/fedora/f34/system-administrators-guide/monitoring-and-automation/OProfile/#s2-oprofile-events
Best Regards,
Sergey
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-03-07 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 10:08 bugzilla [this message]
2022-03-07 22:36 ` [Buildroot] [Bug 14641] oprofile can not find the events files bugzilla
2022-03-08 8:18 ` bugzilla
2022-03-08 12:50 ` bugzilla
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-14641-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox