Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761012AbYGOBcY (ORCPT ); Mon, 14 Jul 2008 21:32:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757902AbYGOBcR (ORCPT ); Mon, 14 Jul 2008 21:32:17 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:58323 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757783AbYGOBcP (ORCPT ); Mon, 14 Jul 2008 21:32:15 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Steven Rostedt Cc: Andrew Morton , Randy Dunlap , Elias Oltmanns , LKML , Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Clark Williams , Linus Torvalds , Jon Masters References: <87zlop7bp6.fsf@denkblock.local> <20080710132832.38cc5048.randy.dunlap@oracle.com> <20080711121655.05810822.akpm@linux-foundation.org> <20080711153740.b86acadd.akpm@linux-foundation.org> Date: Mon, 14 Jul 2008 18:26:43 -0700 In-Reply-To: (Steven Rostedt's message of "Mon, 14 Jul 2008 21:08:32 -0400 (EDT)") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SA-Exim-Connect-IP: 24.130.11.59 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-DCC: XMission; sa01 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Steven Rostedt X-Spam-Relay-Country: X-Spam-Report: * -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 T_TM2_M_HEADER_IN_MSG BODY: T_TM2_M_HEADER_IN_MSG * -0.2 BAYES_40 BODY: Bayesian spam probability is 20 to 40% * [score: 0.2467] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa01 1397; Body=1 Fuz1=1 Fuz2=1] * 0.5 XM_Body_Dirty_Words Contains a dirty word * 0.0 XM_SPF_Neutral SPF-Neutral Subject: Re: [PATCH -v2] ftrace: Documentation X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100) X-SA-Exim-Scanned: Yes (on mgr1.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1136 Lines: 29 Steven Rostedt writes: > Actually it is a /debug (or /sys/mount/debug if you prefer) file. Got it. I haven't ever actually seen anyone use debugfs. > I'd be interested in knowing who would want namespaces in traces. I've > basically only used tracing to see "what's happening in the kernel here?". > Where I only use the pid to differentiate between the tasks I know are > running. > Hence, tracing is much like printk. Does it really matter with these > outputs. But ftrace is pluggable, pid namespaces may matter in future > plugins. So it would not be hard to capture the pid namespace in mount or even look at current to get it (although the last is a little odd). I'm not at all certain if it makes sense. If this is something an ordinary user could use then we definitely want to do something. Is tracing possible without inserting kernel modules? Eric -- 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/