Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752861AbZKTJPL (ORCPT ); Fri, 20 Nov 2009 04:15:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751593AbZKTJPJ (ORCPT ); Fri, 20 Nov 2009 04:15:09 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:55113 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750907AbZKTJPJ (ORCPT ); Fri, 20 Nov 2009 04:15:09 -0500 Message-ID: <4B065DFB.8090909@cn.fujitsu.com> Date: Fri, 20 Nov 2009 17:14:35 +0800 From: Li Zefan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 MIME-Version: 1.0 To: Ingo Molnar CC: Pekka Enberg , 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 References: <4B064AF5.9060208@cn.fujitsu.com> <20091120081440.GA19778@elte.hu> <84144f020911200019p4978c8e8tc593334d974ee5ff@mail.gmail.com> <20091120083053.GB19778@elte.hu> <4B0657A4.2040606@cs.helsinki.fi> <4B06590C.7010109@cn.fujitsu.com> <20091120090353.GE19778@elte.hu> In-Reply-To: <20091120090353.GE19778@elte.hu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 999 Lines: 23 Ingo Molnar wrote: > * Li Zefan wrote: > >>> (2) doing "perf kmem record" on machine A (think embedded here) and >>> then "perf kmem report" on machine B. I haven't tried kmemtrace-user >>> for a while but it did support both of them quite nicely at some >>> point. >> Everything needed and machine-specific will be recorded in perf.data, >> so this should already been supported. I'll try it. > > Right now the DSOs are not recorded in the perf.data - but it would be > useful to add it and to turn perf.data into a self-sufficient capture of > all relevant data, which can be analyzed on any box. > But still 'perf kmem' should function better than kmemtrace-user, since the latter records no more than raw trace data. -- 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/