From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Ingo Molnar <mingo@elte.hu>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool
Date: Fri, 20 Nov 2009 12:31:35 +0200 [thread overview]
Message-ID: <4B067007.8070607@cs.helsinki.fi> (raw)
In-Reply-To: <20091120101305.GA16781@elte.hu>
Ingo Molnar kirjoitti:
> * Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>
>> Hi Ingo,
>>
>> On Fri, Nov 20, 2009 at 11:01 AM, Ingo Molnar <mingo@elte.hu> wrote:
>>> But ... even without that, perf is really fast and is supposed to build
>>> fine even in minimal (embedded) environments, so you can run it on the
>>> embedded board too. That's useful to get live inspection features like
>>> 'perf top', 'perf stat' and 'perf probe' anyway.
>> Maybe I'm just too damn lazy but if I don't go through the trouble of
>> building my kernel on the box, I sure don't want to do that for perf
>> either. [...]
>
> Well you'll need 'perf' on that box anyway, to be able to do 'perf kmem
> record'.
/me turns brains on
You're right, of course. With kmemtrace-user, I just copied the raw
trace file from /sys/kernel. I wonder if that's a good enough reason to
keep kmemtrace bits around?
Pekka
--
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>
next prev parent reply other threads:[~2009-11-20 10:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 7:53 Li Zefan
2009-11-20 7:53 ` [PATCH 2/2] tracing: Remove kmemtrace tracer Li Zefan
2009-11-20 8:20 ` Pekka Enberg
2009-11-20 8:24 ` Li Zefan
2009-11-20 8:27 ` Pekka Enberg
2009-11-20 8:31 ` Li Zefan
2009-11-20 8:14 ` [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Ingo Molnar
2009-11-20 8:19 ` Pekka Enberg
2009-11-20 8:30 ` Ingo Molnar
2009-11-20 8:47 ` Pekka Enberg
2009-11-20 8:53 ` Li Zefan
2009-11-20 9:03 ` Ingo Molnar
2009-11-20 9:14 ` Li Zefan
2009-11-20 14:42 ` Arnaldo Carvalho de Melo
2009-11-20 16:41 ` Ingo Molnar
2009-11-20 17:52 ` Arnaldo Carvalho de Melo
2009-11-23 6:51 ` Ingo Molnar
2009-11-23 7:22 ` Peter Zijlstra
2009-11-23 7:33 ` Ingo Molnar
2009-11-23 14:37 ` Arnaldo Carvalho de Melo
2009-11-23 14:32 ` Arnaldo Carvalho de Melo
2009-11-20 9:01 ` Ingo Molnar
2009-11-20 9:15 ` Pekka Enberg
2009-11-20 10:13 ` Ingo Molnar
2009-11-20 10:31 ` Pekka Enberg [this message]
2009-11-20 10:49 ` Ingo Molnar
2009-11-23 14:46 ` Steven Rostedt
2009-11-23 17:53 ` Ingo Molnar
2009-11-20 8:20 ` Li Zefan
2009-11-20 8:54 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-20 8:55 ` [RFC][PATCH 1/2] " Ingo Molnar
2009-11-20 9:11 ` Li Zefan
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=4B067007.8070607@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=acme@redhat.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox