[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39d1df95-a695-1041-38a6-b94d1eee9eb2@gliwa.com>
Date: Tue, 24 Jul 2018 11:59:28 +0200
From: Claudio <claudio.fontana@...wa.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: ftrace global trace_pipe_raw
Hello Steven,
I am doing correlation of linux sched events, following all tasks between cpus,
and one thing that would be really convenient would be to have a global
trace_pipe_raw, in addition to the per-cpu ones, with already sorted events.
I would imagine the core functionality is already available, since trace_pipe
in the tracing directory already shows all events regardless of CPU, and so
it would be a matter of doing the same for trace_pipe_raw.
But is there a good reason why trace_pipe_raw is available only per-cpu?
Would work in the direction of adding a global trace_pipe_raw be considered
for inclusion?
Thank you,
Claudio
Powered by blists - more mailing lists