Hi, I am working on adding support in perf for many events for a particular architecture. As it is, there are thousands of events to add, with potentially many more.
Instead of treating each event as a separate raw event number (e.g., "perf stat -e rXXXXX ."), I wondering if there is any existing support in the perf infrastructure to support event attributes? For example, if I have an event that represents "DDR hits", meaning all accesses to DDR, and I want to add support for DDR hits from a particular source, do I need to add a perf event for every possible source (e.g., "DDR access from source A", "DDR access from source B", .), or is there a way to specify attributes for the event, in order to keep the number of events to a reasonable level, and also make it easier for the user? Something like "perf stat -e rXXXXX -source A" The "Source" is one example of an attribute. There are several others. If you wanted to add support for all of those variations without using some kind of attribute, the number of events would be difficult to implement in a "flat" way, due to the huge number of events required. Also, it seems not very useable. On the perf wiki, I see mention of "sub-events" and "unit masks", which could be applicable, but I cannot find any other info or examples on them, or see the related kernel code. I would like to use a kernel module to extend this, if possible. Also, potentially related are modifiers (but it looks like those may not be something I could extend). I'm not sure. Any info or suggestions are appreciated. Thanks, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
