RFC perf: persistent events prototype
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 of 2 patches 26 repliesIn review
1 of 2 patches is in this archive. The cover letter announces 2.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/2 | x86, mce: Make MCE tracepoint persistent eventarch/ include/ | +5 | 0 replies |
Reviews trailers per patch
The patch has no Reviewed-by or Acked-by.
| Patch | Borislav Petkov |
|---|---|
| 2/2 | Not-yet-signed-off-by |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH 0/2] perf: persistent events prototype
Hi,
here is my first stab at persistent events. And since it is a first one, there's no special tricks but simply all subsystems which init before perf and have declared static tracepoints, simply mark some of them as persistent and perf enables them when inits.
I haven't tested this yet and will do so when I get to work next week but I'm sending it out now so that I can get your thoughts on this and whether this is an agreeable direction I'm taking.
Couple of yet unresolved issues I see with this:
* persistent events are enabled unconditionally on all cpus and while this makes sense for MCEs tracing, do we still want to be flexible here and supply a cpumask instead?
* what happens if there's no consumer for the traced data, the easiest would be to do nothing and let it get truncated in the trace buffer with newer data overwriting the oldest sample?
* what about other events, and most importantly, what about hw events for which we take a PMU and want to make them persistent at the same time and it so happens that after making a couple of events persistent, we run out of PMUs and make the perf tool almost useless since persistent events are hogging all the hardware resources?
* btw, perf and ftrace really need to get married :)
/me ducks now...
Thanks.