Re: --mmap-pages option seemingly has no effect to help with LOST samples

[David Ahern <dsahern@xxxxxxxxx>]

On 6/22/12 2:23 PM, Maynard Johnson wrote:
> On 06/22/2012 02:44 PM, David Ahern wrote:
> > On 6/22/12 1:20 PM, Maynard Johnson wrote:
> > > I was seeing this on both my Intel Core 2 Duo and an IBM POWER7 server, both running RHEL 6.2.  Also tried on another POWER7 running RHEL 6.3 beta, and got the same results.  I found another POWER server that had RHEL 6.2 but was temporarily booted on a 3.5 kernel and ran the test there -- the counts were good there. :-)  Just to be sure, I rebooted that system to the stock RHEL 6.2 kernel and reproduced the problem.  So it seems there's an upstream fix for this.  Can someone help me find the commit?
> >
> > emails crossing in the ether.
> >
> > 2.6.32 is real early in the perf history. I flipped a system to the Fedora 14 2.6.35.14 kernel -- and it does not handle multiple events either. With Arnaldo's last updates I did notice something curious about the events:
> Yes, I realize that 2.6.32 is early perf, but a lot of our customers are stuck with it.  Too bad I didn't discover this before RHEL 6.3 GA'ed.  Again, I'm hoping that someone in the perf community watching this list might be able to point to an upstream commit for the problem so we can push that fix into RHEL 6.4 (at least).  Is there someone you would suggest to be cc'ed?

I maintain a backport to WRL3. As part of debugging your problem I found 
my backport version is susceptible as well. In my testing I had only 
looked at single events, not multiple. For my version adding :uk did not 
help, but :u did. I'll find some time to do a bisect and see if I can 
find commit(s) that fix the problem, but it will be a background task.

David




--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html