Date: Tue, 7 Dec 2010 23:58:23 -0500 From: Mark Johnston <markjdb@gmail.com> To: Dag-Erling Sm??rgrav <des@des.no> Cc: mdf@FreeBSD.org, freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: coretemp(4)/amdtemp(4) and sysctl nodes Message-ID: <20101208045823.GB35615@mark-desktop-bsd.mark-home> In-Reply-To: <86r5dsq5oc.fsf@ds4.des.no> References: <AANLkTikNJ29AcE1fBXqq_atUU8PQBz9VUos0V%2BwBFQJs@mail.gmail.com> <86r5dsq5oc.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101208045823.GB35615>