[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090826184116.GA20283@infradead.org>
Date: Wed, 26 Aug 2009 14:41:16 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
Jason Baron <jbaron@...hat.com>, linux-kernel@...r.kernel.org,
mingo@...e.hu, laijs@...fujitsu.com, rostedt@...dmis.org,
jiayingz@...gle.com, mbligh@...gle.com, lizf@...fujitsu.com,
Heiko Carstens <heiko.carstens@...ibm.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [PATCH 08/12] add trace events for each syscall entry/exit
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists