Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] OT: Using oprofile on buildroot system
Date: Wed, 20 Aug 2014 15:33:38 +0000 (UTC)	[thread overview]
Message-ID: <lt2f4i$f16$1@ger.gmane.org> (raw)

I'm trying to get oprofile 0.9.9 running on my ARM9 biuldroot target.
I've enabled oprofile support in my kernel (2.6.33), and the oprofile
package builds fine, and the binaries are where they should be on the
target system.  But, when I try to run opcontrol, it appears to be
trying to load a runtime kernel module:

  # opcontrol --init
  modprobe: chdir(/lib/modules): No such file or directory
  modprobe: chdir(/lib/modules): No such file or directory
  Kernel doesn't support oprofile
 
The oprofile docs say you can enable oprofile support either as a
module or built-in, and I have done the latter -- so despite what
opcontrol says, my kernel _does_ support oprofile. 

I don't have loadable module support enabled in my kernel so of course
modprobe isn't going to work. 

Does anybody have any hints on getting oprofile running?

Any ideas on what module opcontrol might be trying to load?

[I've asked these questions on the oprofile mailing list, but haven't
gotten any response.]

-- 
Grant Edwards               grant.b.edwards        Yow! Why are these athletic
                                  at               shoe salesmen following
                              gmail.com            me??

             reply	other threads:[~2014-08-20 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 15:33 Grant Edwards [this message]
2014-08-20 15:59 ` [Buildroot] OT: Using oprofile on buildroot system Grant Edwards

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='lt2f4i$f16$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox