From: Apparao, P. K <pad...@in...> - 2006-11-21 18:39:04
|
Hi, =20 I think you should enable frame pointers in your kernel config. =20 =20 - Padma =20 =20 ________________________________ From: opr...@li... [mailto:opr...@li...] On Behalf Of Wen shu Tang (wentang) Sent: Thursday, November 16, 2006 4:45 PM To: opr...@li... Subject: callgraph support on x86 =20 Hi, I am fairly newbie to this. I am trying to profile kernel modules for optimization.=20 =20 I am currently running on this system. uname -a Linux svbu-vm-host-1 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 i686 i386 GNU/Linux My version of oprofile is 0.9.2 When trying to: opcontrol --callgraph=3D1 I get this error message: Call-graph profiling unsupported on this kernel/hardware =20 Everywhere I looked seems to indicate that I should be getting callgraph support. Is there something missing that I need to do in order to get callgraphs =20 Thank you for your help and time in advance. =20 Wen Shu Tang =20 Wen Shu Tang =20 |
From: Wen S. <we...@ci...> - 2006-11-28 01:54:40
|
Hi, I am still struggling with the same problem. On my current system, I = do not get any call-graph support, nor can I set any events. Oprofile = falls back to timer interrupt mode. I am running oprofile on intel = xeons. Here is the /proc/cpuinfo. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5150 @ 2.66GHz stepping : 6 cpu MHz : 2666.745 cache size : 4096 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge = mca cmov pat pse36 clflush dts acpi mmx fxsr ss e sse2 ss ht tm syscall lm pni monitor ds_cpl est tm2 cx16 xtpr bogomips : 5339.10 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual In the source code in cpu_type.c: if (model > 0xd)=20 return CPU_RTC;=20 This looks like for my particular type of cpu, oprofile falls back to = RTC mode. Does this mean that intel xeons are not supported by oprofile? = How do I work around it? Please help out, I really feel like I hit a wall so far with oprofile. = Any hints would be highly appreciated. Thanks in advance. Wen Shu "Apparao, Padmashree K" <pad...@in...> wrote in = message = news:AF3...@fm....= .. Hi, =20 I think you should enable frame pointers in your kernel config. =20 =20 - Padma =20 =20 -------------------------------------------------------------------------= ----- From: opr...@li... = [mailto:opr...@li...] On Behalf Of Wen = shu Tang (wentang) Sent: Thursday, November 16, 2006 4:45 PM To: opr...@li... Subject: callgraph support on x86 =20 Hi, I am fairly newbie to this. I am trying to profile kernel modules = for optimization.=20 =20 I am currently running on this system. uname -a Linux svbu-vm-host-1 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT = 2006 i686 i686 i386 GNU/Linux My version of oprofile is 0.9.2 When trying to: opcontrol --callgraph=3D1 I get this error message: Call-graph profiling unsupported on this = kernel/hardware =20 Everywhere I looked seems to indicate that I should be getting = callgraph support. Is there something missing that I need to do in order = to get callgraphs =20 Thank you for your help and time in advance. =20 Wen Shu Tang =20 Wen Shu Tang =20 -------------------------------------------------------------------------= ----- = -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to = share your opinions on IT & business topics through brief surveys - and earn cash = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV -------------------------------------------------------------------------= ----- _______________________________________________ oprofile-list mailing list opr...@li... https://lists.sourceforge.net/lists/listinfo/oprofile-list |
From: Hiro Y. <hyo...@mi...> - 2006-11-28 07:43:59
|
Hi, I think your processor is very new. core 2, right? From: "Wen Shu" <we...@ci...> Subject: Re: callgraph support on x86 Date: Mon, 27 Nov 2006 17:54:09 -0800 > Hi, I am still struggling with the same problem. On my current system, I do not get any call-graph support, nor can I set any events. Oprofile falls back to timer interrupt mode. I am running oprofile on intel xeons. Here is the /proc/cpuinfo. > > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 15 > model name : Intel(R) Xeon(R) CPU 5150 @ 2.66GHz > stepping : 6 > cpu MHz : 2666.745 > cache size : 4096 KB > physical id : 0 > siblings : 2 > core id : 0 > cpu cores : 2 > fpu : yes > fpu_exception : yes > cpuid level : 10 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr ss > e sse2 ss ht tm syscall lm pni monitor ds_cpl est tm2 cx16 xtpr > bogomips : 5339.10 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > > > In the source code in cpu_type.c: > if (model > 0xd) > return CPU_RTC; it should return CPU_CORE_2 Regards, Hiro |