From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752767AbZHZSl0 (ORCPT ); Wed, 26 Aug 2009 14:41:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752588AbZHZSlZ (ORCPT ); Wed, 26 Aug 2009 14:41:25 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:48640 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752447AbZHZSlZ (ORCPT ); Wed, 26 Aug 2009 14:41:25 -0400 Date: Wed, 26 Aug 2009 14:41:16 -0400 From: Christoph Hellwig To: Mathieu Desnoyers Cc: Peter Zijlstra , Frederic Weisbecker , Hendrik Brueckner , Jason Baron , linux-kernel@vger.kernel.org, mingo@elte.hu, laijs@cn.fujitsu.com, rostedt@goodmis.org, jiayingz@google.com, mbligh@google.com, lizf@cn.fujitsu.com, Heiko Carstens , Martin Schwidefsky Subject: Re: [PATCH 08/12] add trace events for each syscall entry/exit Message-ID: <20090826184116.GA20283@infradead.org> References: <20090825141547.GE6114@nowhere> <20090825160237.GG4639@cetus.boeblingen.de.ibm.com> <20090825162004.GA25058@Krystal> <20090825165912.GI6114@nowhere> <20090825173107.GJ6114@nowhere> <20090825183119.GC2448@Krystal> <1251267669.7538.1195.camel@twins> <20090826170812.GC21456@Krystal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090826170812.GC21456@Krystal> User-Agent: Mutt/1.5.19 (2009-01-05) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 26, 2009 at 01:08:12PM -0400, Mathieu Desnoyers wrote: > Nah. And I start to feel comfortable with syscall entry/exit being only > be traced for userspace threads. But as I pointed out in a follow-up > email, the lack of sys_*() tracing for invocation from within the kernel > might be problematic. This is actually my main point. We do not support system calls from kernelspace anymore. All the macros to do real system calls are gone, and there are very very few places left calling sys_foo as normal function calls. An how exactly is calling sys_foo as a normal function call different from calling do_foo or vfs_foo?