From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 8 04:56:02 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16EC61065670 for ; Wed, 8 Dec 2010 04:56:02 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-iw0-f196.google.com (mail-iw0-f196.google.com [209.85.214.196]) by mx1.freebsd.org (Postfix) with ESMTP id CE1D88FC17 for ; Wed, 8 Dec 2010 04:56:01 +0000 (UTC) Received: by iwn36 with SMTP id 36so298073iwn.7 for ; Tue, 07 Dec 2010 20:56:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=vEk9zq2B2PIogcqF+2rJ9bN01av7j0nLFcggBlhUpuc=; b=FJt09sIAHie/dso8aGdcw4mFcD7LzniZt3CYi92P/GRndFxAoAUnIOZdRAA0EE1a8P ysnv6y0K15McHU/X2HoDb/D1uCM8XSGajk/H/v7KXz81scxPf4Ma5/3KnWCmxWDkLl4a /OFrUsXhT03/tPrqcK+FbX6TFCN+hzZJKBmyw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hL7L2HSzIKDKDdf+cMPNfy/lQze1GhszEjmM3ZSVh1twdab8JLGDZJjnBXorL5Ab5c SILvEaqo+bjgl5e+0iCAnAiUkDOexIWd+Ma/ppd549mGLVa5gG2OJTCbQ9RI3mTn/QS/ 6rWGKof1GWgLq6KCnU8yc8jBcC40rnLyu/8bo= Received: by 10.42.174.138 with SMTP id v10mr43670icz.91.1291784160074; Tue, 07 Dec 2010 20:56:00 -0800 (PST) Received: from mark-desktop-bsd.mark-home (CPE00044b162033-CM00111ae61918.cpe.net.cable.rogers.com [99.236.163.170]) by mx.google.com with ESMTPS id d21sm166095ibg.9.2010.12.07.20.55.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 07 Dec 2010 20:55:59 -0800 (PST) Date: Tue, 7 Dec 2010 23:58:23 -0500 From: Mark Johnston To: Dag-Erling Sm??rgrav Message-ID: <20101208045823.GB35615@mark-desktop-bsd.mark-home> References: <86r5dsq5oc.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86r5dsq5oc.fsf@ds4.des.no> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: mdf@FreeBSD.org, freebsd-hackers Subject: Re: coretemp(4)/amdtemp(4) and sysctl nodes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2010 04:56:02 -0000 On Wed, Dec 08, 2010 at 04:55:47AM +0100, Dag-Erling Sm??rgrav wrote: > I can't speak for amdtemp, but if coretemp used its own context instead > of its parent's context, it would show up as dev.coretemp.X.temperature > instead of dev.cpu.Y.temperature, where X is not necessarily equal to Y. Aren't the dev.cpu.X and the coretemp sysctls matched up by the use of SYSCTL_CHILDREN(device_get_sysctl_tree(pdev)) in coretemp's sysctl definition? What does the sysctl context have to do with identifying the parent oid? -Mark