Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752758AbZKTKtl (ORCPT ); Fri, 20 Nov 2009 05:49:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752612AbZKTKtl (ORCPT ); Fri, 20 Nov 2009 05:49:41 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:32967 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752610AbZKTKtk (ORCPT ); Fri, 20 Nov 2009 05:49:40 -0500 Date: Fri, 20 Nov 2009 11:49:20 +0100 From: Ingo Molnar To: Pekka Enberg Cc: Li Zefan , Arnaldo Carvalho de Melo , Frederic Weisbecker , Steven Rostedt , Peter Zijlstra , Eduard - Gabriel Munteanu , LKML , "linux-mm@kvack.org" Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Message-ID: <20091120104920.GA12634@elte.hu> References: <4B064AF5.9060208@cn.fujitsu.com> <20091120081440.GA19778@elte.hu> <84144f020911200019p4978c8e8tc593334d974ee5ff@mail.gmail.com> <20091120083053.GB19778@elte.hu> <4B0657A4.2040606@cs.helsinki.fi> <20091120090134.GD19778@elte.hu> <84144f020911200115g14cfa3b5k959f8751001b8b35@mail.gmail.com> <20091120101305.GA16781@elte.hu> <4B067007.8070607@cs.helsinki.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B067007.8070607@cs.helsinki.fi> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1330 Lines: 35 * Pekka Enberg wrote: > Ingo Molnar kirjoitti: > >* Pekka Enberg wrote: > > > >>Hi Ingo, > >> > >>On Fri, Nov 20, 2009 at 11:01 AM, Ingo Molnar 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? Not really. If then a light-weight recording app could be made but i'd rather wait for actual usecases to pop up. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/