From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753071AbZHLO3r (ORCPT ); Wed, 12 Aug 2009 10:29:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753046AbZHLO3q (ORCPT ); Wed, 12 Aug 2009 10:29:46 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:46114 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753030AbZHLO3q (ORCPT ); Wed, 12 Aug 2009 10:29:46 -0400 Date: Wed, 12 Aug 2009 16:29:17 +0200 From: Ingo Molnar To: Jason Baron Cc: Frederic Weisbecker , LKML , Lai Jiangshan , Steven Rostedt , Peter Zijlstra , Mathieu Desnoyers , Jiaying Zhang , Martin Bligh , Li Zefan , Masami Hiramatsu Subject: Re: [GIT PULL] tracing: Syscalls trace events + perf support Message-ID: <20090812142917.GA19882@elte.hu> References: <1250016545-6601-1-git-send-email-fweisbec@gmail.com> <20090812091133.GA21655@elte.hu> <20090812110307.GA806@elte.hu> <20090812111436.GA24263@elte.hu> <20090812142516.GB2711@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090812142516.GB2711@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jason Baron wrote: > On Wed, Aug 12, 2009 at 01:14:36PM +0200, Ingo Molnar wrote: > > another thing: could we please also have a generic, highlevel > > tracepoint (in addition to the specific tracepoints) that > > enumerates the raw syscall Nr and the parameters it gets - in a > > single tracepoint? > > The specific tracepoints, are all layered on 2 (entry, exit) > generic tracepoints already. So this shouldn't be too hard...The > parameters it gets might be tricky, since there are a variable > number b/w different syscalls? We should just list all ~6 of them. It's up to the sampling entity to decide which ones (if any) is relevant. At least on x86 the syscall arguments will always have a value when the syscall entry code is called. (they are in GP registers) Ingo