From owner-freebsd-current Fri Aug 23 15:11:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FA9437B400 for ; Fri, 23 Aug 2002 15:11:30 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id E24CF43E6E for ; Fri, 23 Aug 2002 15:11:29 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: from iguana.icir.org (localhost [127.0.0.1]) by iguana.icir.org (8.12.3/8.11.3) with ESMTP id g7NMBRIb082685; Fri, 23 Aug 2002 15:11:27 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.12.3/8.12.3/Submit) id g7NMBRTG082684; Fri, 23 Aug 2002 15:11:27 -0700 (PDT) (envelope-from rizzo) Date: Fri, 23 Aug 2002 15:11:27 -0700 From: Luigi Rizzo To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: how to compute the skew between TSC in SMP systems ? Message-ID: <20020823151127.A82640@iguana.icir.org> References: <20020823144256.A82380@iguana.icir.org> <30687.1030139048@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <30687.1030139048@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Aug 23, 2002 at 11:44:08PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ok, i'll look into the ACPI counter. But you still did not tell me why trying to determine the TSC skew cannot be done reliably ... On Fri, Aug 23, 2002 at 11:44:08PM +0200, Poul-Henning Kamp wrote: > In message <20020823144256.A82380@iguana.icir.org>, Luigi Rizzo writes: > > >I want to find performance problems in the kernel, and to this purpose, > >sometimes i need to timestamp events in the kernel using the > >least-intrusive technique i can use, and hopefully get reasonably ... > Alternatively, consider using "basic-block profiling" (see kernbb(8) and > gcc docs), that will tell you not only how many instructions but also > _which_ instructions are executed. this one does not give timing info at all, and it is probably also on the "terribly intrusive" side of the spectrum... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message