When I try to use oprofile on 2.6.19, it does not seem to work:
[EMAIL PROTECTED] tmp]$ sudo opcontrol --no-vmlinux
[EMAIL PROTECTED] 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.
[EMAIL PROTECTED] tmp]$ ls /dev/oprofile/
1 backtrace_depth buffer_watershed dump stats
2 buffer cpu_buffer_size enable
3 buffer_size cpu_type pointer_size
[EMAIL PROTECTED] tmp]$ cat /var/lib/oprofile/oprofiled.log
oprofiled started Tue Jan 9 21:41:02 2007
kernel pointer size: 8
[EMAIL PROTECTED] 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
[EMAIL PROTECTED] tmp]$
Gert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/