On Wed, 2010-02-03 at 15:54 +0100, Stephane Eranian wrote: > > PEBS is still very useful because it guarantees the state you capture > is at retirement of an instruction which caused the event. > > PEBS also gets way more interesting on Nehalem because of the > ability to capture where cache misses occur. That's the load latency > feature. You need to support that.
Simple things first. But yeah, we'll get to load-latency eventually. > I believe you would need to abstract this in a generic fashion so it > could be used on other architectures, such as AMD with IBS. Right, Robert said he was working on IBS, I've still not made up my mind on how to represent IBS properly, its a bit of a weird thing. > On Nehalem, it requires the following: > > - only works if you sample on MEM_INST_RETIRED:LATENCY_ABOVE_THRESHOLD. Yeah, and then you get to decode the data source thingy, not really a nice interface. Also, it mostly contains L3 information, not L2/L1. > - the threshold must be programmed into a dedicated MSR. The extra > difficulty is that this MSR is shared between CPU when HT is on. Lovely :/ One way is to program it to the lowest of the two and simply discard events afterwards. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
