From: Gert Vervoort <gert.vervoort@hccnet.nl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: oprofile broken on 2.6.19
Date: Tue, 09 Jan 2007 21:46:54 +0100 [thread overview]
Message-ID: <45A3FF3E.7060109@hccnet.nl> (raw)
When I try to use oprofile on 2.6.19, it does not seem to work:
[gert@apollo tmp]$ sudo opcontrol --no-vmlinux
[gert@apollo tmp]$ sudo opcontrol --start
/usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or directory/usr/bin/opcontrol: line 911:
/dev/oprofile/0/event: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/count: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/kernel: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/user: No such file or directory
/usr/bin/opcontrol: line 911: /dev/oprofile/0/unit_mask: No such file or directory
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/oprofiled.log
Daemon started.
Profiler running.
[gert@apollo tmp]$ ls /dev/oprofile/
1 backtrace_depth buffer_watershed dump stats
2 buffer cpu_buffer_size enable
3 buffer_size cpu_type pointer_size
[gert@apollo tmp]$ cat /var/lib/oprofile/oprofiled.log
oprofiled started Tue Jan 9 21:41:02 2007
kernel pointer size: 8
[gert@apollo tmp]$ uname -a
Linux apollo 2.6.19 #1 PREEMPT Thu Nov 30 18:52:13 CET 2006 x86_64 x86_64 x86_64 GNU/Linux
[gert@apollo tmp]$
Gert
next reply other threads:[~2007-01-09 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 20:46 Gert Vervoort [this message]
2007-01-10 17:43 ` oprofile broken on 2.6.19 Tomas Carnecky
2007-01-10 17:32 ` Gert Vervoort
2007-01-11 14:37 ` Tomas Carnecky
2007-01-11 14:47 ` Eric Dumazet
2007-01-11 17:17 ` Tomas Carnecky
2007-01-10 17:45 ` Tomas Carnecky
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=45A3FF3E.7060109@hccnet.nl \
--to=gert.vervoort@hccnet.nl \
--cc=linux-kernel@vger.kernel.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 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.