Re: Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen

[Rusty Russell <rusty@xxxxxxxxxxxxxxx>]

On Mon, 2005-02-28 at 13:22 +0100, harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
wrote:
> Why have two separate mechanisms when the mechanism required for
> hotplug can be used to build the tree from scratch?

The only difference would be the transport for hotplug events, which is
infrastructure which needs to exist anyway to transport other
information between domains.

We'll see when the code's finished, but I see the code being:

        __init boot_devtree_setup()
        {
                devtree_add(boot_devtree_ptr);
        }

        hotplug_receive_event()
        {
                receive data
                if (op == ADD)
                        devtree_add(data);
                else if (op == REMOVE)
                        devtree_remove(data);
        }

ie. the mere difference in transport should be a few lines of code.
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel