On Wed, May 15, 2013 at 04:20:46PM +0200, Stephane Eranian wrote: > Hi, > > Based on our testing, it appears the corruption occurs only > when the MEM_* events are used and only on the sibling > counter. In other words, if HT0 has MEM_* in cntr0, then > HT1 cntr0 cannot be used, otherwise whatever is there may > get corrupted.
Ah, great. That is the least horrid case :-) > So I think we could enhance Andi's initial patch > to handle this case instead of blacklist those events. They are > very important events. Will you take a stab at it? I suppose you'll have to make each counter have a shared resource and have the mem_*_retired events mark the resource taken. Also, did you test what happens when you turn SMT off in the BIOS so you get double the amount of counters; do we then leak into CNTn+4 or is all well again? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
