|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] KVM call agenda for Tuesday 7 |
Date: | Tue, 07 Feb 2012 10:33:44 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15 |
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 /devicesYeah, 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
[Prev in Thread] | Current Thread | [Next in Thread] |