victor jimenez <betaband...@gmail.com> wrote on 05/21/2009 02:12:18 AM:
> Hi Corey, > > calling to pfm_arch_clear_pmd_ovfl_cond() does not make any problem in > the case of a context switch out, but it does when you only stop the > counters and want to read them right after stopping them. In that > case, because they have been set to 0 (by > pfm_arch_clear_pmd_ovfl_cond()), when they are read in > perfmon_rw.c:634 you get a 0 value all the time. > > I am not sure why the Intel people changed a bit the pmd_save_pmds() > function which they use in stop_save(), buy they basically seem to > have replicated the function without the call to > pfm_arch_clear_pmd_ovfl_cond(). > > Regards, > Victor Hello Victor, Thank you for the explanation. After looking at this again, it looks like your patch is fine and is following in similar footsteps to x86. Stephane, can you please commit Victor's patch? Regards, - Corey Corey Ashford Software Engineer IBM Linux Technology Center, Linux Toolchain Beaverton, OR 503-578-3507 cjash...@us.ibm.com ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
