lkml.org 
[lkml]   [2011]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 9/10] sh: Use struct syscore_ops instead of sysdev class and sysdev
    On Tue, Mar 22, 2011 at 11:00:56PM +0100, Kay Sievers wrote:
    > On Wed, 2011-03-23 at 06:49 +0900, Paul Mundt wrote:
    > > The comment at the top of sys.c says:
    > >
    > > * sys.c - pseudo-bus for system 'devices' (cpus, PICs, timers, etc)
    >
    > Which is what we need to get rid of. It does not make any sense on the
    > global picture to have anything like that exported to userspace.
    >
    So far I haven't heard any rationale for why it doesn't. Exporting CPU
    state to userspace certainly makes sense, and the sysdev model has worked
    reasonably for CPUs, memory nodes, etc.

    > People should really stop messing around in /sys for optimization
    > purposes. We have a common device model, and need to use it. Sysdevs do
    > not fit into that model.
    >
    > I can't tell how that fits into your use case, but please use something
    > else than sysfs, if you need device information exported, but you can't
    > use "struct device".
    >
    As long as CPU state is present in sysfs people will be tied to it for
    per-CPU kobjects and the like, and until something concrete is proposed
    for what to do about these cases there's not much chance of sysdevs going
    away.

    Once cpufreq, timekeeping, and NUMA node state have migrated to whatever
    the driver model folks find acceptable, I'll happily follow suit.


    \
     
     \ /
      Last update: 2011-03-22 23:27    [W:0.041 / U:0.056 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site