From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rientjes@google.com,
dchinner@redhat.com
Subject: Re: [PATCH] oom: add tracepoints for oom_score_adj
Date: Fri, 9 Dec 2011 09:33:23 +0900 [thread overview]
Message-ID: <20111209093323.977284db.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20111209084103.e3fea1f7.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 9 Dec 2011 08:41:03 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Thu, 08 Dec 2011 12:33:35 -0500
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
see Documentation/trace/event.txt 5. Event filgtering
> >
> > Now, both ftrace and perf have good filter feature. Isn't this enough?
> >
>
> Could you make patch ? Then, I stop this and go other probelm.
>
Hmm, core of patch should be like this. But need some works on
- How to debug oom in Documenation especially for trace-cmd users.
- Other trace points sutable for 'task' tracing. maybe 'exit, stop, freeze' ?
- at creating new task, what other members should be printed out ?
- At renaming...don't we need reason for renaming ?
Hm. BTW, do you know how to write filtering in
/etc/sysconfig/trace-cmd.config ?
prev parent reply other threads:[~2011-12-09 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 0:54 KAMEZAWA Hiroyuki
2011-12-07 1:22 ` David Rientjes
2011-12-07 1:27 ` KAMEZAWA Hiroyuki
2011-12-07 1:55 ` [PATCH v3] " KAMEZAWA Hiroyuki
2011-12-07 16:52 ` [PATCH] " KOSAKI Motohiro
2011-12-08 1:47 ` KAMEZAWA Hiroyuki
2011-12-08 6:32 ` [PATCH v4] " KAMEZAWA Hiroyuki
2014-02-04 8:39 ` Peter Zijlstra
2011-12-08 17:33 ` [PATCH] " KOSAKI Motohiro
2011-12-08 23:41 ` KAMEZAWA Hiroyuki
2011-12-09 0:33 ` KAMEZAWA Hiroyuki [this message]
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=20111209093323.977284db.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox