I was thinking about this a little further. So you suggest that theHow does this work for events? The "@hisi_sicl,cpa@event_foo" looks
metric expression contains PMU name per term, like
"cpu_atom@instructions@ / cpu_atom@cycles@" - how would/could this work
for PMUs with more complex naming, like the form hisi_siclXXX_cpa_YYY?
Would we use the "Unit" expression for the metric name, like
"@hisi_sicl,cpa@event_foo"?
strange, shouldn't it be "hisi_sicl,cpa@event_foo@" but then hisi_sicl
looks like an event name.
Arnaldo could you take a look at doing this?Can that be added to the MAINTAINERS file? I suppose it is ok underBTW, which git repo/branch do you guys use for dev? I thought that itCurrent development is here now:
would be acme git, but Namhyung says "We moved to new repos from acme to
perf/perf-tools and perf/perf-tools-next" - where is repo "perf"?
https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/log/?h=perf-tools-next__;!!ACWV5N9M2RV99hQ!OQDHOClSjd6nVZhmgzrK3RwzXuQpP54QhqyIKpITa_MFD4PLdS7yPYSnvInFja9nrFx9Sd-UnlsJ6XUqAh4$
"PERFORMANCE EVENTS SUBSYTEM", since the two would-be git repos listed
under that same entry would be pretty obvious in purpose.