Thanks Baruch,
But, I am still hitting the same issue.
I am using SuSE 2.6.5, but oprofile code looks
similar.
so i manually made that small change from if
(cpu_model > 3) to if (cpu_model > 100), and did a
make modules and make modules_install.
Then inserted the fresh oprofile module.
# opcontrol --setup --event=CPU_CLK_UNHALTED
You cannot specify any performance counter events
because OProfile is in timer mode.
--- Baruch Even <baruch@xxxxxxxxx> wrote:
The patch that worked for me against 2.6.6 is
attached.
Baruch
arch/i386/oprofile/nmi_int.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: 2.6.6/arch/i386/oprofile/nmi_int.c
===================================================================
--- 2.6.6.orig/arch/i386/oprofile/nmi_int.c
+++ 2.6.6/arch/i386/oprofile/nmi_int.c
@@ -313,7 +313,7 @@ static int __init p4_init(void)
{
__u8 cpu_model = current_cpu_data.x86_model;
- if (cpu_model > 3)
+ if (cpu_model > 100)
return 0;
#ifndef CONFIG_SMP
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html