Greg KH <[EMAIL PROTECTED]> writes: [dropped perfmon list because gmane messed it up and it's apparently closed anyways]
> Is there any way to just provide a basic framework that everyone can > agree on and then add on more stuff as time goes on? Do we have to have > every different processor/arch with support to start with? I think the real problem are not the architectures (the processor adaption layer is usually relatively straight forward IIRC), but the excessive functionality implemented by the user interface. It would be really good to extract a core perfmon and start with that and then add stuff as it makes sense. e.g. core perfmon could be something simple like just support to context switch state and initialize counters in a basic way and perhaps get counter numbers for RDPMC in ring3 on x86[1] Next step could be basic event on overflow/underflow support. Then more features as they make sense, with clear rationale what they're good for and proper step by step patches. -Andi [1] On x86 we urgently need a replacement to RDTSC for counting cycles. - 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/
