From owner-freebsd-arch@FreeBSD.ORG Tue Jul 10 19:01:46 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9B3E16A468; Tue, 10 Jul 2007 19:01:46 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.freebsd.org (Postfix) with ESMTP id 9A98013C4FA; Tue, 10 Jul 2007 19:01:46 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by ironport2.ambrisko.com with ESMTP; 10 Jul 2007 11:28:13 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id l6AIX1Pf049967; Tue, 10 Jul 2007 11:33:01 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id l6AIX0xl049962; Tue, 10 Jul 2007 11:33:00 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200707101833.l6AIX0xl049962@ambrisko.com> In-Reply-To: <20070708081511.GX1221@funkthat.com> To: John-Mark Gurney Date: Tue, 10 Jul 2007 11:33:00 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Rui Paulo , Andre Oppermann , Perforce Change Reviews , "Constantine A. Murenin" , Shteryana Shopova , freebsd-arch@freebsd.org Subject: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD (was: Re: PERFORCE change 123040 for review) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2007 19:01:46 -0000 John-Mark Gurney writes: | Constantine A. Murenin wrote this message on Sat, Jul 07, 2007 at 21:43 -0400: | > Hardware sensors tree is going to be pretty deep down. Under sysctl(8) | > the variable names will look like this: | > | > hw.sensors.lm0.temp0 | > | > whereas in reality, the tree has five levels: | > | > hw.sensors.lm0.temp.0 | | I'm curious, why do we want/need these in the kernel as opposed to a | userland library/utility to provide this info? I agree. There are so many different flavours of HW monitoring chips and several tools that can read them live in ports. Lots of them are slightly different, intefaces can be i2c or direct I/O. We are already somewhat battling with the various ways IPMI controllers can be attached to the system. Now in the case of IPMI there is a good win in providing a device driver interface for the HW and user land tools to get info. out of them. I don't see a win with this in the various HW monitoring chips. Doug A.