Hi Lukas,
----- Original Message -----
> [...]
> All noted and on my TODO. I'll start looking into the conflicting
> cases as well!
Cool. OOC, is it possible to ask PAPI what hardware counters are
enabled? (IOW, without relying on the state kept in-memory, in the
daemon, as a result of changes it made itself, but rather by asking
the hardware/kernel?).
If so, that would be great to use as the value for the control "enable"
metric, instead of simply exporting whatever state changes we've made in
the PMDA (and assuming everything was disabled when it started, which
may not have been the case). I'm also not 100% sure what the meaning
of the value exported with the "disable" metric is? AIUI, we export the
last observed (stored) disable-request-string - is that right?
> > Thanks Lukas! Also, you mentioned earlier today those per-process
> > metrics were proceeding nicely, and that the next update was around
> > the corner - please include in that one the spec file fix to switch
> > this on by default for Fedora builds, and a back-port of the s390(x)
> > fixes - these'll live in build/rpm/fedora.spec for the next release.
>
> I've backported the fixes (in lberk/papi currently), and I'll send
Is that ready to pull in or would you rather it wait? Just starting on
merging all the current work now.
cheers.
--
Nathan
|