Messages in this thread | | | Date | Mon, 6 May 2019 10:46:18 -0400 | From | Steven Rostedt <> | Subject | Re: [PATCH 4/7] sched: Add sched_load_rq tracepoint |
| |
On Mon, 6 May 2019 15:42:00 +0100 Qais Yousef <qais.yousef@arm.com> wrote:
> I can control that for the wrappers I'm introducing. But the actual tracepoint > get the 'trace_' part prepended automatically by the macros. > > ie DECLARE_TRACE(pelt_rq, ...) will automatically generate a function called > trace_pelt_se(...) > > Or am I missing something?
No trace comes from the trace points.
So basically, we are going back to having tracepoints without associated trace events. Which basically is just saying "we want trace events here, but don't want an API". Of course, we can create a module that can attach to them and create the trace events as well.
I'm not a big fan of this, but I'll let Peter decide.
-- Steve
| |