From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760641Ab0FKVws (ORCPT ); Fri, 11 Jun 2010 17:52:48 -0400 Received: from rcsinet10.oracle.com ([148.87.113.121]:61050 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760624Ab0FKVwq (ORCPT ); Fri, 11 Jun 2010 17:52:46 -0400 Date: Fri, 11 Jun 2010 14:51:16 -0700 From: Randy Dunlap To: Chase Douglas Cc: Frederic Weisbecker , Prasad , Pekka Enberg , Eduard - Gabriel Munteanu , Soeren Sandmann , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org, kernel-team@lists.ubuntu.com Subject: Re: Tracing configuration review Message-Id: <20100611145116.72c88387.randy.dunlap@oracle.com> In-Reply-To: <1276034434.8645.56.camel@cndougla-ubuntu> References: <1274815906.9757.83.camel@cndougla-ubuntu> <20100525201259.GA5370@nowhere> <1274821799.9346.17.camel@cndougla-ubuntu> <20100608103517.ac380ad4.randy.dunlap@oracle.com> <1276034434.8645.56.camel@cndougla-ubuntu> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Auth-Type: Internal IP X-Source-IP: acsinet15.oracle.com [141.146.126.227] X-CT-RefId: str=0001.0A090209.4C12AFEA.01B1:SCFMA922111,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 08 Jun 2010 18:00:34 -0400 Chase Douglas wrote: > On Tue, 2010-06-08 at 10:35 -0700, Randy Dunlap wrote: > > Hi Chase, > > > > Would you mind sharing your final tracing config options? > > Sure. > > Our source tree for Maverick encompasses all our major supported > platforms in one git branch. Thus, we have one common config file and a > bunch of arch and flavour (generic, server, virtual, pae) specific > config files. One note about the common configs: if a config option > would not exist because an option in a specific config file is set a > certain way, then you can ignore it for that specific arch/flavour. For > example, the common config has CONFIG_DYNAMIC_FTRACE=y, but the armel > config has "CONFIG_FUNCTION_TRACER is not set" so the former would not > have any affect on armel builds. > > You can find the source branch at > http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=summary > > $ grep -Ir "TRAC[EI]" debian.master/config > ./amd64/config.common.amd64:CONFIG_FUNCTION_TRACER=y > ./amd64/config.common.amd64:CONFIG_STACK_TRACER=y > ./i386/config.common.i386:CONFIG_FUNCTION_TRACER=y > ./i386/config.common.i386:CONFIG_STACK_TRACER=y > ./armel/config.common.armel:# CONFIG_FUNCTION_TRACER is not set > ./armel/config.common.armel:# CONFIG_STACK_TRACER is not set > ./config.common.ubuntu:# CONFIG_BACKTRACE_SELF_TEST is not set > ./config.common.ubuntu:CONFIG_BLK_DEV_IO_TRACE=y > ./config.common.ubuntu:# CONFIG_BOOT_TRACER is not set > ./config.common.ubuntu:CONFIG_CAN_PM_TRACE=y > ./config.common.ubuntu:CONFIG_CAPI_TRACE=y > ./config.common.ubuntu:CONFIG_CONTEXT_SWITCH_TRACER=y > ./config.common.ubuntu:CONFIG_DYNAMIC_FTRACE=y > ./config.common.ubuntu:CONFIG_EVENT_TRACING=y > ./config.common.ubuntu:CONFIG_FTRACE=y > ./config.common.ubuntu:CONFIG_FTRACE_MCOUNT_RECORD=y > ./config.common.ubuntu:CONFIG_FTRACE_NMI_ENTER=y > ./config.common.ubuntu:# CONFIG_FTRACE_STARTUP_TEST is not set > ./config.common.ubuntu:CONFIG_FTRACE_SYSCALLS=y > ./config.common.ubuntu:CONFIG_FUNCTION_GRAPH_TRACER=y > ./config.common.ubuntu:CONFIG_GENERIC_TRACER=y > ./config.common.ubuntu:CONFIG_HAVE_ARCH_TRACEHOOK=y > ./config.common.ubuntu:CONFIG_HAVE_DYNAMIC_FTRACE=y > ./config.common.ubuntu:CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y > ./config.common.ubuntu:CONFIG_HAVE_FTRACE_NMI_ENTER=y > ./config.common.ubuntu:CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y > ./config.common.ubuntu:CONFIG_HAVE_FUNCTION_TRACER=y > ./config.common.ubuntu:CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y > ./config.common.ubuntu:CONFIG_HAVE_MMIOTRACE_SUPPORT=y > ./config.common.ubuntu:CONFIG_HAVE_SYSCALL_TRACEPOINTS=y > ./config.common.ubuntu:# CONFIG_IRQSOFF_TRACER is not set > ./config.common.ubuntu:CONFIG_IWLWIFI_DEVICE_TRACING=y > ./config.common.ubuntu:# CONFIG_KMEMTRACE is not set > ./config.common.ubuntu:# CONFIG_KSYM_TRACER is not set > ./config.common.ubuntu:CONFIG_MMIOTRACE=y > ./config.common.ubuntu:# CONFIG_MMIOTRACE_TEST is not set > ./config.common.ubuntu:CONFIG_NETFILTER_XT_TARGET_TRACE=m > ./config.common.ubuntu:CONFIG_NOP_TRACER=y > ./config.common.ubuntu:CONFIG_PM_TRACE=y > ./config.common.ubuntu:CONFIG_PM_TRACE_RTC=y > ./config.common.ubuntu:# CONFIG_RCU_TRACE is not set > ./config.common.ubuntu:CONFIG_SCHED_TRACER=y > ./config.common.ubuntu:# CONFIG_SCSI_IPR_TRACE is not set > ./config.common.ubuntu:CONFIG_STACKTRACE=y > ./config.common.ubuntu:CONFIG_STACKTRACE_SUPPORT=y > ./config.common.ubuntu:# CONFIG_SYSPROF_TRACER is not set > ./config.common.ubuntu:CONFIG_TRACEPOINTS=y > ./config.common.ubuntu:CONFIG_TRACER_MAX_TRACE=y > ./config.common.ubuntu:CONFIG_TRACE_IRQFLAGS_SUPPORT=y > ./config.common.ubuntu:CONFIG_TRACING=y > ./config.common.ubuntu:CONFIG_TRACING_SUPPORT=y > ./config.common.ubuntu:# CONFIG_TREE_RCU_TRACE is not set > ./config.common.ubuntu:CONFIG_USER_STACKTRACE_SUPPORT=y > ./config.common.ubuntu:# CONFIG_VXGE_DEBUG_TRACE_ALL is not set > ./config.common.ubuntu:# CONFIG_WORKQUEUE_TRACER is not set > > Some of the above is not FTRACE. I also snipped the matches in > config.common.ports because they are slightly different due to what the > ports architectures support, but they should be pretty similar. > > Please let me know if anything stands out at you as incorrect. I'm a bit surprised by one (family) of kconfig symbols here: PM_TRACE=y, PM_TRACE_RTC=y That enables low-level kernel developer debugging code. Other than that, the rest make sense to me. thanks. [I don't know about that "armel" stuff.] --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***