Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751667Ab3DYFx4 (ORCPT ); Thu, 25 Apr 2013 01:53:56 -0400 Received: from LGEMRELSE7Q.lge.com ([156.147.1.151]:51685 "EHLO LGEMRELSE7Q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750758Ab3DYFxz (ORCPT ); Thu, 25 Apr 2013 01:53:55 -0400 X-AuditID: 9c930197-b7bb3ae000000fa9-80-5178c4effb46 From: Namhyung Kim To: "zhangwei\(Jovi\)" Cc: Ingo Molnar , Pekka Enberg , Steven Rostedt , Arnaldo Carvalho de Melo , Peter Zijlstra , Paul Mackerras , Namhyung Kim , LKML , Frederic Weisbecker , Jiri Olsa , David Ahern , Stephane Eranian Subject: Re: [RFC 00/14] perf tools: Introduce new 'ftrace' command References: <1366705872-12132-1-git-send-email-namhyung@kernel.org> <1366732681.9609.157.camel@gandalf.local.home> <20130424065018.GC27551@gmail.com> <87a9oob6i2.fsf@sejong.aot.lge.com> <5177BEC7.4020906@huawei.com> Date: Thu, 25 Apr 2013 14:53:51 +0900 In-Reply-To: <5177BEC7.4020906@huawei.com> (zhangwei's message of "Wed, 24 Apr 2013 19:15:19 +0800") Message-ID: <87obd39mvk.fsf@sejong.aot.lge.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1475 Lines: 33 On Wed, 24 Apr 2013 19:15:19 +0800, zhangwei wrote: > On 2013/4/24 17:52, Namhyung Kim wrote: >> I think it'd be great if perf trace can cover both of kernel and user >> spaces. But function tracing in userspace looks impossible IMHO. >> >> So how about changing perf trace to receive proposed sub-commands >> (live/record/show/report) and following options: >> >> --kernel:: do ftrace (for kernel functions) >> --syscall:: do system call tracing (what perf trace does now) >> > "--kernel" make me think it's will trace all event tracepoints, not only ftrace. Well, I'm not sure what's the right name. --kernel-function? > > for "--syscall" option, I always think we should enhance syscall tracing more than now, > like use annotate info when parse syscall event in perf, as other tracepoint does. > we also need read filename user string in kernel space when open syscall tracepoint hit, > record in perf.data, then perf parse it. After these functionality is implemented, > we will don't need a separate syscall tracing tool in perf any more, > just use: perf record -e "syscalls:" -a It's a different story. But I do think it'd better if there's a way to see some of userspace strings like this. Thanks, Namhyung -- 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/