From: Dave Hansen <dave.hansen@intel.com>
To: Davidlohr Bueso <davidlohr@hp.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] mm,tracing: improve current situation
Date: Thu, 03 Apr 2014 15:31:08 -0700 [thread overview]
Message-ID: <533DE12C.9030203@intel.com> (raw)
In-Reply-To: <1396561440.4661.33.camel@buesod1.americas.hpqcorp.net>
On 04/03/2014 02:44 PM, Davidlohr Bueso wrote:
> Now, on a more general scenario, I basically would like to know, 1) is
> this actually useful... I'm hoping that, if in fact something like this
> gets merged, it won't just sit there. 2) What other general data would
> be useful for debugging purposes? I'm happy to collect feedback and send
> out something we can all benefit from.
One thing that would be nice, specifically for the VM, would be to turn
all of the things that touch the /proc/vmstat counters
(count_vm_event(), etc...) in to tracepoints.
I started on it once, but ran in to some header dependency hell and gave
up before I got anything useful.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: Davidlohr Bueso <davidlohr@hp.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] mm,tracing: improve current situation
Date: Thu, 03 Apr 2014 15:31:08 -0700 [thread overview]
Message-ID: <533DE12C.9030203@intel.com> (raw)
In-Reply-To: <1396561440.4661.33.camel@buesod1.americas.hpqcorp.net>
On 04/03/2014 02:44 PM, Davidlohr Bueso wrote:
> Now, on a more general scenario, I basically would like to know, 1) is
> this actually useful... I'm hoping that, if in fact something like this
> gets merged, it won't just sit there. 2) What other general data would
> be useful for debugging purposes? I'm happy to collect feedback and send
> out something we can all benefit from.
One thing that would be nice, specifically for the VM, would be to turn
all of the things that touch the /proc/vmstat counters
(count_vm_event(), etc...) in to tracepoints.
I started on it once, but ran in to some header dependency hell and gave
up before I got anything useful.
next prev parent reply other threads:[~2014-04-03 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:44 [RFC] mm,tracing: improve current situation Davidlohr Bueso
2014-04-03 21:44 ` Davidlohr Bueso
2014-04-03 22:31 ` Dave Hansen [this message]
2014-04-03 22:31 ` Dave Hansen
2014-04-03 23:34 ` Davidlohr Bueso
2014-04-03 23:34 ` Davidlohr Bueso
2014-04-03 23:24 ` Sasha Levin
2014-04-03 23:24 ` Sasha Levin
2014-04-08 15:44 ` Vlastimil Babka
2014-04-08 15:44 ` Vlastimil Babka
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=533DE12C.9030203@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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 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.