There should be a similar case there for PPro machines, and you might
have something other than an Intel Xeon.
The best route to solve your problem is the oprofile irc channel, you
can find its details in the oprofile website.
Baruch
li nux wrote:
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 <[email protected]> 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
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]