Em Mon, Nov 28, 2011 at 06:43:35AM -0800, Arjan van de Ven escreveu:
> > perf_evlist is what you call perf_bundle and perf_evsel is what you call
> > perf_event in powertop.
> > That part of the API should be ok for wider use and is in fact exported
> > in the python binding.
>
> I don't care abo
Em Mon, Nov 28, 2011 at 06:02:27AM -0800, Arjan van de Ven escreveu:
> On 11/28/2011 3:42 AM, Peter Zijlstra wrote:
> > On Mon, 2011-11-28 at 12:03 +0300, Andrew Vagin wrote:
> >> This tracepoint shows how long a task is sleeping in uninterruptible state.
> >> E.g.
> >> It may show how long and wh
>
> perf_evlist is what you call perf_bundle and perf_evsel is what you call
> perf_event in powertop.
>
> That part of the API should be ok for wider use and is in fact exported
> in the python binding.
I don't care about the snake language.
frankly all that's missing is a "safe" accessor libr
On 11/28/2011 3:42 AM, Peter Zijlstra wrote:
> On Mon, 2011-11-28 at 12:03 +0300, Andrew Vagin wrote:
>> This tracepoint shows how long a task is sleeping in uninterruptible state.
>>
>> E.g.
>> It may show how long and where a mutex is waited.
>
> Fair enough, makes one wonder how much it would t
On Mon, 2011-11-28 at 12:03 +0300, Andrew Vagin wrote:
> This tracepoint shows how long a task is sleeping in uninterruptible state.
>
> E.g.
> It may show how long and where a mutex is waited.
Fair enough, makes one wonder how much it would take to make
account_scheduler_latency() go away..
> S
