All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janani Ravichandran <janani.rvchndrn@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Janani Ravichandran <janani.rvchndrn@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: Include postprocessing script for memory allocation tracing
Date: Thu, 27 Oct 2016 11:42:35 -0400	[thread overview]
Message-ID: <49064D60-DE83-4545-960E-5FB5897441C5@gmail.com> (raw)
In-Reply-To: <20161021070832.GE6045@dhcp22.suse.cz>


> On Oct 21, 2016, at 3:08 AM, Michal Hocko <mhocko@kernel.org> wrote:
> 
> Interesting.
> $ cat /debug/tracing/available_tracers 
> function_graph preemptirqsoff preemptoff irqsoff function nop
> 
> Do I have to configure anything specially? And if I do why isn't it any
> better to simply add a start tracepoint and make this available also to
> older kernels?

Well, you just need to enable the function_graph tracer in the tracing directory:
echo function_graph > current_tracer,

set funcgraph-proc in trace_options to get process information:
echo funcgraph-proc > trace_options,

set funcgraph-abstime in trace_options to get timestamp,
echo funcgraph-abstime > trace_options

set all the functions we’d like to observe as filters. For e.g.
echo __alloc_pages_nodemask > set_ftrace_filter

and enable the tracepoints we would like to get information from.

I didn’t add a begin tracepoint for this as Steven Rostedt had suggested
using function graph instead of begin/end tracepoints (we already have
a tracepoint in __alloc_pages_nodemask - trace_mm_page_alloc to get 
some information about the allocation and we can just use function graph 
to see how long __alloc_pages_nodemask() takes).

Janani

> -- 
> Michal Hocko
> SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Janani Ravichandran <janani.rvchndrn@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Janani Ravichandran <janani.rvchndrn@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: Include postprocessing script for memory allocation tracing
Date: Thu, 27 Oct 2016 11:42:35 -0400	[thread overview]
Message-ID: <49064D60-DE83-4545-960E-5FB5897441C5@gmail.com> (raw)
In-Reply-To: <20161021070832.GE6045@dhcp22.suse.cz>


> On Oct 21, 2016, at 3:08 AM, Michal Hocko <mhocko@kernel.org> wrote:
> 
> Interesting.
> $ cat /debug/tracing/available_tracers 
> function_graph preemptirqsoff preemptoff irqsoff function nop
> 
> Do I have to configure anything specially? And if I do why isn't it any
> better to simply add a start tracepoint and make this available also to
> older kernels?

Well, you just need to enable the function_graph tracer in the tracing directory:
echo function_graph > current_tracer,

set funcgraph-proc in trace_options to get process information:
echo funcgraph-proc > trace_options,

set funcgraph-abstime in trace_options to get timestamp,
echo funcgraph-abstime > trace_options

set all the functions we’d like to observe as filters. For e.g.
echo __alloc_pages_nodemask > set_ftrace_filter

and enable the tracepoints we would like to get information from.

I didn’t add a begin tracepoint for this as Steven Rostedt had suggested
using function graph instead of begin/end tracepoints (we already have
a tracepoint in __alloc_pages_nodemask - trace_mm_page_alloc to get 
some information about the allocation and we can just use function graph 
to see how long __alloc_pages_nodemask() takes).

Janani

> -- 
> Michal Hocko
> SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-10-27 16:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 22:24 [RFC] scripts: Include postprocessing script for memory allocation tracing Janani Ravichandran
2016-09-11 22:24 ` Janani Ravichandran
2016-09-12 12:16 ` Michal Hocko
2016-09-12 12:16   ` Michal Hocko
2016-09-13 18:04   ` Janani Ravichandran
2016-09-13 18:04     ` Janani Ravichandran
2016-09-19  9:42     ` Michal Hocko
2016-09-19  9:42       ` Michal Hocko
2016-09-22 15:30       ` Janani Ravichandran
2016-09-22 15:30         ` Janani Ravichandran
2016-09-23  8:07         ` Michal Hocko
2016-09-23  8:07           ` Michal Hocko
2016-10-06 12:00           ` Michal Hocko
2016-10-06 12:00             ` Michal Hocko
2016-10-11 14:43           ` Janani Ravichandran
2016-10-11 14:43             ` Janani Ravichandran
2016-10-15 23:31             ` Janani Ravichandran
2016-10-15 23:31               ` Janani Ravichandran
2016-10-16  7:33               ` Michal Hocko
2016-10-16  7:33                 ` Michal Hocko
     [not found]                 ` <CANnt6X=RpSnuxGXZfF6Qa5mJpzC8gL3wkKJi3tQMZJBZJVWF3w@mail.gmail.com>
2016-10-17 17:31                   ` Janani Ravichandran
2016-10-18 13:13                     ` Michal Hocko
2016-10-18 13:13                       ` Michal Hocko
2016-10-20 23:10                       ` Janani Ravichandran
2016-10-20 23:10                         ` Janani Ravichandran
2016-10-21  7:08                         ` Michal Hocko
2016-10-21  7:08                           ` Michal Hocko
2016-10-27 15:42                           ` Janani Ravichandran [this message]
2016-10-27 15:42                             ` Janani Ravichandran
  -- strict thread matches above, loose matches on Subject: below --
2016-08-19 11:38 Janani Ravichandran
2016-08-19 11:38 ` Janani Ravichandran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49064D60-DE83-4545-960E-5FB5897441C5@gmail.com \
    --to=janani.rvchndrn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.