From owner-freebsd-hackers@FreeBSD.ORG  Tue Mar  2 22:27:49 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 656D716A4CE
	for <freebsd-hackers@freebsd.org>;
	Tue,  2 Mar 2004 22:27:49 -0800 (PST)
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 91B4C43D3F
	for <freebsd-hackers@freebsd.org>;
	Tue,  2 Mar 2004 22:27:48 -0800 (PST)
	(envelope-from ticso@cicely12.cicely.de)
Received: from cicely5.cicely.de (cicely5.cicely.de
	[IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7])	(authenticated bits=0)
	i236RerQ017621
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK)
	for <freebsd-hackers@freebsd.org>;
	Wed, 3 Mar 2004 07:27:46 +0100 (CET)
	(envelope-from ticso@cicely12.cicely.de)
Received: from cicely12.cicely.de (cicely12.cicely.de
	[IPv6:3ffe:400:8d0:301::12])
	by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i236RWuL005630
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <freebsd-hackers@freebsd.org>;
	Wed, 3 Mar 2004 07:27:32 +0100 (CET)
	(envelope-from ticso@cicely12.cicely.de)
Received: from cicely12.cicely.de (localhost [127.0.0.1])
	by cicely12.cicely.de (8.12.10/8.12.10) with ESMTP id i236RVc5082778
	for <freebsd-hackers@freebsd.org>;
	Wed, 3 Mar 2004 07:27:31 +0100 (CET)
	(envelope-from ticso@cicely12.cicely.de)
Received: (from ticso@localhost)
	by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i236RVaG082777
	for freebsd-hackers@freebsd.org; Wed, 3 Mar 2004 07:27:31 +0100 (CET)
	(envelope-from ticso)
Date: Wed, 3 Mar 2004 07:27:31 +0100
From: Bernd Walter <ticso@cicely12.cicely.de>
To: freebsd-hackers@freebsd.org
Message-ID: <20040303062730.GK44313@cicely12.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha
User-Agent: Mutt/1.5.4i
X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham 
	version=2.61
X-Spam-Report: 
	* -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	*      [score: 0.0000]
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	cicely5.cicely.de
Subject: how to get cpu states more than once a second?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: ticso@cicely.de
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2004 06:27:49 -0000

Currently I get the states via kern.cp_time, but this only allows
a granularity of a single second and I need something around 50-100ms.
Application is a LED bargraph which doesn't have the intended effect
with just a single update per second.

-- 
B.Walter                   BWCT                http://www.bwct.de
ticso@bwct.de                                  info@bwct.de