From owner-freebsd-sparc64@FreeBSD.ORG Tue Jul 20 10:54:57 2010 Return-Path: Delivered-To: freebsd-sparc64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00F9D106570B; Tue, 20 Jul 2010 10:54:57 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 39F648FC0C; Tue, 20 Jul 2010 10:54:56 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id o6KAstJu043537; Tue, 20 Jul 2010 12:54:55 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id o6KAstIX043536; Tue, 20 Jul 2010 12:54:55 +0200 (CEST) (envelope-from marius) Date: Tue, 20 Jul 2010 12:54:55 +0200 From: Marius Strobl To: Alexander Motin Message-ID: <20100720105454.GE4706@alchemy.franken.de> References: <4C404018.6040405@FreeBSD.org> <20100716213503.GT4706@alchemy.franken.de> <4C42A5B9.7080901@FreeBSD.org> <20100718142101.GY4706@alchemy.franken.de> <4C433391.4080808@FreeBSD.org> <20100719122423.GA4706@alchemy.franken.de> <4C44694C.9040108@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C44694C.9040108@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@FreeBSD.org Subject: Re: [RFC] Event timers on sparc64/sun4v X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 10:54:57 -0000 On Mon, Jul 19, 2010 at 06:03:40PM +0300, Alexander Motin wrote: > > There is indeed too small info about this. I've found that thing about > edge, you've noticed, also I've found that TICK clock is integer > multiply of STICK. Taking analogy to x86 I may assume that CPUs with > different frequencies still quite likely use same bus frequency (STICK), > or even sharing the same bus, while have different multipliers for core > (TICK) frequency. > It is indeed only an assumption, but it would be strange for CPU > designers to implement one more counter, which is not better then > already existing one. My understanding is that the only advantage of the STICK counter over the TICK one is that the former is always driven by the same frequency across all CPUs in a system, regardless of the frequency the CPUs are running at (as needed in machines equipped with different CPU models or when down throttling). Marius