On 02/07/2012 10:27 AM, Paolo Bonzini wrote:
On 02/07/2012 05:24 PM, Anthony Liguori wrote:
I'm wary of all plans that require to go through all the code once. What about
simply /devices/default/child[...] or something like that?
The paths would be unstable, but maybe that's okay. I'd suggest
doing child[rand()] to avoid the appearance that these paths are in
any way shape or form stable.
Sounds a bit inconvenient for humans (who in the end are those who debug things
:)).
There are tons of human readable paths to a single object so I don't think it's
a problem. But no big deal with way since /devices/default should go away anyway.
BTW, I would like to change /i440fx to /devices/i440fx, so that we
will have clean namespaces:
/block
/chardev
/clocks
/devices
Yeah, this makes sense. By clocks, you mean things like rtc_clock,
vm_clock, etc? Not the omap clocks which happen to live in /clocks in
your series?
No, I really meant the OMAP clocks. :) Basically if you have an abstract
subclass TYPE_FOOS of TYPE_OBJECT, its instances would reside under /foos or
something easily related to "foos".
Hrm, I don't like that very much.
OMAP clocks are devices. Don't they belong in the devices hierarchy under the
omap-clocks branch?
The fact that they aren't DeviceState's is because DeviceState is a pile of
cruft. Perhaps we should introduce a more streamlined Device base class and
rename DeviceState to LegacyDevice or something like that.
Regards,
Anthony Liguori
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
