From: Ceylan, T. <Tol...@sa...> - 2006-03-14 02:45:45
|
Thanks for the reply,=20 cpuinfo shows "Xeon (TM) 3.6Ghz", is this more like a generic description that an actual CPU detection?=20 On the box, which is working cpuinfo shows "Xeon (TM) MP 3.0Ghz" How do I determine if the kernel identifies a CPU? Is there a specific text that I should look for in dmesg output or in cpuinfo? -----Original Message----- From: William Cohen [mailto:wc...@nc...] Sent: Mon 3/13/2006 8:32 PM To: Ceylan, Tolga Cc: opr...@li... Subject: Re: Intel Xeon =20 Ceylan, Tolga wrote: > Hello; >=20 > I've been using oprofile on HP DL560 server with 2 x Intel Xeon MP > 3.00Ghz > processors. The server is loaded with Redhat AS4.0, and things > work as expected. >=20 > However, recently I realized that on a DL380 hardware with 2 x Intel > Xeon 3.60Ghz hardware on RedHat AS40, the CPU type is set to "timer".=20 > These servers they all have the same SMP kernels. So, the difference > is only the hardware. >=20 > I am using stock RedHat kernel. Do you think the problem is due to > an old oprofile module in Redhat stock kernels?=20 >=20 > Has anybody had any "timer" problems with Xeon processors with > oprofile before? >=20 > Thanks, >=20 > Tolga Ceylan You have a newer model processor than the RHEL4 kernel knows about.=20 OProfile needs to identify the processor to determine what kind of=20 performance monitoring hardware the processor has. If OProfile can't=20 identify the processor, it falls back on the timer interrupt mechanism.=20 /proc/cpuinfo should show the differences between the machines. Upstream kernels identify the Xeon processors. This change should be=20 back ported to Red Hat kernel at some point. -Will |