Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932158AbWIOSef (ORCPT ); Fri, 15 Sep 2006 14:34:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932167AbWIOSef (ORCPT ); Fri, 15 Sep 2006 14:34:35 -0400 Received: from mx1.redhat.com ([66.187.233.31]:18614 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932158AbWIOSee (ORCPT ); Fri, 15 Sep 2006 14:34:34 -0400 Date: Fri, 15 Sep 2006 14:34:32 -0400 From: "Frank Ch. Eigler" To: linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108] Message-ID: <20060915183432.GJ4577@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 24 Hi - On Fri, Sep 15, 2006 at 07:31:48PM +0100, Alan Cox wrote: > Ar Gwe, 2006-09-15 am 13:08 -0400, ysgrifennodd Frank Ch. Eigler: Yeah, or something. :-) > > Alan Cox writes: > > - where 1000-cycle int3-dispatching overheads too high > > Why are your despatching overheads 1000 cycles ? (and if its due to int3 > why are you using int 3 8)) Smart teams from IBM and Hitachi have been hammering away at this code for a year or two now, and yet (roughly) here we are. There have been experiments involving plopping branches instead of int3's at probe locations, but this is self-modifying code involving multiple instructions, and appears to be tricky on SMP/preempt boxes. - FChE - 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/