Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752823AbZKTIyK (ORCPT ); Fri, 20 Nov 2009 03:54:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751661AbZKTIyJ (ORCPT ); Fri, 20 Nov 2009 03:54:09 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:60899 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750715AbZKTIyI (ORCPT ); Fri, 20 Nov 2009 03:54:08 -0500 Message-ID: <4B06590C.7010109@cn.fujitsu.com> Date: Fri, 20 Nov 2009 16:53:32 +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: Pekka Enberg CC: Ingo Molnar , 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> In-Reply-To: <4B0657A4.2040606@cs.helsinki.fi> 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: 1245 Lines: 30 Pekka Enberg wrote: > Ingo Molnar kirjoitti: >> Regarding patch 2 - can we set some definitive benchmark threshold for >> that? I.e. a list of must-have features in 'perf kmem' before we can >> do it? 100% information and analysis equivalency with kmemtrace-user >> tool? > > I'd be interested to hear Eduard's comment on that. > > That said, I'll try to find some time to test "perf kmem" and provide > feedback on that. I can ACK the patch when I'm happy with the output. :-) > > I'm mostly interested in two scenarios: (1) getting a nice report on > worst fragmented call-sites (perf kmem needs symbol lookup) and This will be done in next version. > (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. -- 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/