From owner-freebsd-current@FreeBSD.ORG Mon Jul 5 06:59:50 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1A6B106566C for ; Mon, 5 Jul 2010 06:59:50 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id 780298FC13 for ; Mon, 5 Jul 2010 06:59:50 +0000 (UTC) Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 7BBC7613F for ; Mon, 5 Jul 2010 07:57:36 +0000 (UTC) Date: Mon, 5 Jul 2010 07:59:08 +0100 From: Bruce Cran To: freebsd-current@freebsd.org Message-ID: <20100705075908.000025b8@unknown> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Dummy timecounter being chosen under Xen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 06:59:50 -0000 I upgraded to -CURRENT on a Xen machine yesterday, and found that that the clock wasn't being updated because the dummy timecounter was being used: kern.timecounter.choice: TSC(-100) dummy(-1000000) kern.timecounter.hardware: dummy Shouldn't the TSC have been chosen since it has a higher quality? -- Bruce Cran