Andi, Thanks for the response.
I am not familiar with "config/config1", but I infer from your message that I would make folders in sysfs for different event groups (?) and then have a file for each event that is a bit field that can be parsed. As an alternative, is there anything to prevent encoding the attributes in the event ID itself? I think there are 64 bits to use. Some of those could be interpreted in a way specific to the event. I can see advantages and disadvantage to both. Both ways seem a little convoluted from a user point of view. Seems like a more intuitive way would have been from the command line; ie, provide a way to pass info from the command line that could be interpreted in a way specific to the event. I'm sure that was probably considered, and there is a good reason that method wasn't chosen, but I do wonder... Can you point me to the Intel uncore drivers you mentioned? Thanks again, Chris -----Original Message----- From: Andi Kleen [mailto:a...@firstfloor.org] Sent: Wednesday, March 27, 2013 8:32 PM To: Freehill Christopher-RAT063 Cc: linux-perf-users Subject: Re: perf event attrributes Freehill Christopher-RAT063 <rat...@freescale.com> writes: > > Any info or suggestions are appreciated. The perf model for this is to use bit fields in config/config1 and then declare those in sysfs, so that they can be set as cpu/foo=1,bar=2/ The kernel driver then extracts those fields. This only supports numerical values, not string enumerations. You can see the Intel uncore drivers as a example doing this extensively. -Andi -- a...@linux.intel.com -- Speaking for myself only -- 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
