Re: RE???[PATCH] sched: Add trace for task wake up latency and leave running time

2020-09-15 Thread Steven Rostedt
On Thu, 3 Sep 2020 09:49:25 +0100 Mel Gorman wrote: > If state is to be accumulated between multiple tracepoints then the > primary options are BPF, systemtap, trace-cmd for offline analysis or Note, ftrace now has histograms which use the "synthetic events" that Peter mentioned, which can give

Re: RE???[PATCH] sched: Add trace for task wake up latency and leave running time

2020-09-03 Thread Mel Gorman
On Thu, Sep 03, 2020 at 09:42:32AM +0200, pet...@infradead.org wrote: > > Maybe I need to explain the reason that why I add two trace point. > > when using perf tool or Ftrace sysfs to capture the task wake-up latency > > and the task leaving running queue time, usually the trace data is too >

Re: RE：[PATCH] sched: Add trace for task wake up latency and leave running time

2020-09-03 Thread peterz
On Wed, Sep 02, 2020 at 10:35:34PM +, gengdongjiu wrote: > > NAK, that tracepoint is already broken, we don't want to proliferate the > > broken. > > Sorry, What the meaning that tracepoint is already broken? Just that, the tracepoint is crap. But we can't fix it because ABI. Did I tell

RE：[PATCH] sched: Add trace for task wake up latency and leave running time

2020-09-02 Thread gengdongjiu
Hi Peter， Sorry for the late response. > > > diff --git a/include/linux/sched.h b/include/linux/sched.h index > > 93ecd930efd3..edb622c40a90 100644 > > --- a/include/linux/sched.h > > +++ b/include/linux/sched.h > > @@ -1324,6 +1324,13 @@ struct task_struct { > > /* CPU-specific state of

Re: [PATCH] sched: Add trace for task wake up latency and leave running time

2020-08-21 Thread Peter Zijlstra
> diff --git a/include/linux/sched.h b/include/linux/sched.h > index 93ecd930efd3..edb622c40a90 100644 > --- a/include/linux/sched.h > +++ b/include/linux/sched.h > @@ -1324,6 +1324,13 @@ struct task_struct { > /* CPU-specific state of this task: */ > struct thread_struct