Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD

On Wednesday, 11 July 2007 at 19:51:10 +0200, Alexander Leidinger wrote:
Quoting "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx> (Wed, 11 Jul 2007 17:33:51 +0000):

In message <20070711190546.4b202080@deskjail>, Alexander Leidinger writes:
Quoting "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx> (Wed, 11 Jul 2007 13:54:40 +0000):

You are focusing on physical devices which are specially build as a
sensor for some specific stuff. I put my focus on the kernel framework
which allows to unify the handling of sensoric data from kernel
devices.

I'm trying to point out that your kernel framework belongs in userland.

It's not my framework.

There is no benefit from having it in the kernel.

You need to get some information out of the kernel somehow (you cut
this part of my mail). And as far as I understand the high level
description (presentation in the net) of this framework, this does this
in an unified way. Do you propose to get the information out of the
kernel in a non-uniform way?

I think he wants to say that you could have a broader look at this
problem. Placing the code into kernel is not a necessary requriemet
here to create a unified framework. It can be done much easier in
the user environment. Or don't you forget a mocrokernel approach?

--
======================================================================
- Best regards, Nikolay Pavlov. <<<-----------------------------------
======================================================================

_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: sensors fun..
    ... The goal of this framework is ... IMO to "collect" all this data in the kernel and provide a single ... point of contact for the userland to query this in-kernel data. ... I will answer to your mail where I talked about access to ISA stuff as time permits, and I try to do it in a verbose way so that the picture about Constantine's sensors framework is more clear. ...
    (freebsd-arch)
  • Re: LTT user input
    ... > to understand the kernel or debugging their own applications. ... framework could serve them all too. ... LTT it is, the idea being that tracing the system should disrupt it as ... however be done using the dynamic tracepoints provided by dprobes, ...
    (Linux-Kernel)
  • Re: Frameworks [WAS: Cost of developing a device driver]
    ... in the kernel, there were issues with the DW drivers I developed that I ... >> Just because Windows kernel development is stuck in the stone age doesn't ... > actually love to see a good framework for Windows kernel development (I ... > developers take existing code for a driver and turn it into a new driver. ...
    (microsoft.public.development.device.drivers)
  • Re: LTT user input
    ... > 'why not use the auditing framework for tracing?'. ... Looking for a common base was certainly easier before one tracing ... >> be asked by people not willing or capable of compiling a patched kernel ... What got many people interested in DTrace was hardly a polished 400 ...
    (Linux-Kernel)
  • Re: Porting OpenBSDs sysctl hw.sensors framework to FreeBSD
    ... Sensor hardware is not context-free and selfidentifying like PCI and ... I put my focus on the kernel framework ... needs to be handled in userland. ... cam to use the sensors framework to present interesting data of SCSI ...
    (freebsd-arch)