Re: [RFC PATCH] x86, oprofile: fix P4 oprofile CPU setup bug

[Jaswinder Singh Rajput]

On Sun, 2009-04-05 at 23:38 +0200, Ingo Molnar wrote:

> The real fix would be to go to the right abstraction level and 
> realize how these MSRs are set up by the oprofile code, and put all 
> the MSR reads and writes into one non-preempt section.
> 
> Could you please test the patch below? (Totally untested and 
> everything.) Please dont just check whether the warning went away, 
> but also whether Oprofile still works correctly on your P4/HT box.
> 

This fixed the warning, thanks :-)

oprofile is still not working properly may be because of F10 update
issues:
Stopping profiling.
warning: /usr/lib/libpng12.so.0.34.0 could not be found.
warning: /usr/lib/libpurple.so.0.5.4 could not be found.
warning: /vmlinux-unknown could not be found.
warning: [heap] (tgid:3215 range:0x806f000-0x8091000) could not be found.
warning: [heap] (tgid:3243 range:0x806f000-0x8091000) could not be found.
warning: [heap] (tgid:3325 range:0x806f000-0x809b000) could not be found.
warning: [heap] (tgid:3336 range:0x805d000-0x807e000) could not be found.
warning: [heap] (tgid:3510 range:0x806f000-0x8091000) could not be found.
warning: [heap] (tgid:4736 range:0x806f000-0x8091000) could not be found.
warning: [heap] (tgid:5376 range:0x8058000-0x80a8000) could not be found.
bfd_get_section_contents:get_debug:: Bad value

--
JSR

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/