Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758973AbZA2PfY (ORCPT ); Thu, 29 Jan 2009 10:35:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758633AbZA2Pet (ORCPT ); Thu, 29 Jan 2009 10:34:49 -0500 Received: from fg-out-1718.google.com ([72.14.220.158]:45321 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754282AbZA2Pes convert rfc822-to-8bit (ORCPT ); Thu, 29 Jan 2009 10:34:48 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=U1E6M8vlbQRfiYmaDkaqCzFFoXcH8Ijv5Jzl0UBCoWCrTKhulaPxAOKbx/N8SkAw7x 0uX5XoKfT7TYZ5Fhkx6zhQq4xK5Vt+OgkHvfUbuDgd2XP5zhBrVXfojXujt16uPDP+25 PSNbzTy5iO0RWgWbCUhEr/43xbKELFvQkAO7k= MIME-Version: 1.0 In-Reply-To: <20090129150934.GF6512@elte.hu> References: <497F69A4.2070007@intel.com> <20090127224303.GB5850@nowhere> <20090127225048.GA4652@nowhere> <20090129140451.GM24391@elte.hu> <20090129143120.GS24391@elte.hu> <20090129150934.GF6512@elte.hu> Date: Thu, 29 Jan 2009 16:34:46 +0100 Message-ID: Subject: Re: [PATCH] tracer for sys_open() - sreadahead From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Weisbecker?= To: Ingo Molnar , Roland McGrath , utrace-devel@redhat.com Cc: "Kok, Auke" , Linux Kernel Mailing List , powertop ml , Arjan van de Ven , srostedt@redhat.com, Arnaldo Carvalho de Melo , "Frank Ch. Eigler" , Neil Horman , Ananth N Mavinakayanahalli Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1679 Lines: 47 2009/1/29 Ingo Molnar : > > * Fr?d?ric Weisbecker wrote: > >> 2009/1/29 Ingo Molnar : >> >> >> >> Several people talked me about utrace and gave some examples about it in >> >> this discussion. The Api is very convenient to fetch syscall numbers, >> >> arguments and return values. And the hooks are done in the generic core >> >> code, so it is arch independent. >> >> >> >> The only drawback I can see is that it is not yet merged upstream, in >> >> need of in-kernel users. If it only depends on this condition, we could >> >> be these users... >> >> >> >> What do you think? >> > >> > sure - how do the minimal bits/callbacks look like which enable syscall >> > tracing? I know you are talking about the only necessary bits from utrace to have the syscalls tracing. But I can't answer you better than would the utrace people. And actually I'm not sure the utrace bits for syscall tracing can be isolated from the rest of its core. Anyway, I will let the utrace guy answer to it :-) >> There is a very straightforward example provided by Ananth in there: >> http://lkml.org/lkml/2009/1/28/59 > > I mean, how does the infrastructure patch look like - what code does this > add to the kernel - just to get the syscall tracing bits. Lets get some > progress here - it's clear that tracing syscalls is good, we just need to > do it and look at actual patches. > > Ingo > -- 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/