On Wed, 16 Jan 2019 09:00:00 +0100
Claudio wrote:
> Indeed the perf event interface would be awesome, if only it would support
> tracing all processes.
>
> Unfortunately for my use case, it can only trace one process on any cpus, or
> all processes on one (1) cpu.
>
> I guess for some kind
Hi Steven, happy new year,
On 12/19/2018 05:37 PM, Steven Rostedt wrote:
> On Wed, 19 Dec 2018 12:32:41 +0100
> Claudio wrote:
>
I would imagine the core functionality is already available, since
trace_pipe
in the tracing directory already shows all events regardless of
On Wed, 19 Dec 2018 12:32:41 +0100
Claudio wrote:
> >>
> >> 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.
> >
Hi Steven,
going back to this old theme to clarify a bit what I was trying to achieve:
On 07/24/2018 04:23 PM, Steven Rostedt wrote:
> On Tue, 24 Jul 2018 11:58:18 +0200
> Claudio wrote:
>
>> Hello Steven,
>>
>> I am doing correlation of linux sched events, following all tasks between
>>
Hello Steve,
thank you for your answer,
On 07/24/2018 04:25 PM, Steven Rostedt wrote:
> On Tue, 24 Jul 2018 10:23:16 -0400
> Steven Rostedt wrote:
>
>>>
>>> Would work in the direction of adding a global trace_pipe_raw be considered
>>> for inclusion?
>>
>> The design of the lockless ring
Hello Steve,
thank you for your answer,
On 07/24/2018 04:25 PM, Steven Rostedt wrote:
> On Tue, 24 Jul 2018 10:23:16 -0400
> Steven Rostedt wrote:
>
>>>
>>> Would work in the direction of adding a global trace_pipe_raw be considered
>>> for inclusion?
>>
>> The design of the lockless ring
On Tue, 24 Jul 2018 10:23:16 -0400
Steven Rostedt wrote:
> >
> > Would work in the direction of adding a global trace_pipe_raw be considered
> > for inclusion?
>
> The design of the lockless ring buffer requires not to be preempted,
> and that the data cannot be written to from more than one
On Tue, 24 Jul 2018 10:23:16 -0400
Steven Rostedt wrote:
> >
> > Would work in the direction of adding a global trace_pipe_raw be considered
> > for inclusion?
>
> The design of the lockless ring buffer requires not to be preempted,
> and that the data cannot be written to from more than one
On Tue, 24 Jul 2018 11:58:18 +0200
Claudio wrote:
> 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
On Tue, 24 Jul 2018 11:58:18 +0200
Claudio wrote:
> 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
10 matches
Mail list logo
