Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

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

To: Rusty Russell <rusty@xxxxxxxxxxxxxxx>, harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Re: Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen
From: harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 28 Feb 2005 14:08:58 +0100 (CET)
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Jeremy Katz <katzj@xxxxxxxxxx>, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 28 Feb 2005 13:13:59 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Reply-to: harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
You are thinking about the code differences from the point of view of the code 
running inside the domain.  What about the code outside the domain, for 
example, is the code required to remove a device from one domain and give it to 
another going to have to be different depending on whether the target domain 
has been booted yet?


> Message date : Feb 28 2005, 01:01 PM
> From : "Rusty Russell" <rusty@xxxxxxxxxxxxxxx>
> To : harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Copy to : "Anthony Liguori" <aliguori@xxxxxxxxxx>, "Keir Fraser" 
> <Keir.Fraser@xxxxxxxxxxxx>, "Jeremy Katz" <katzj@xxxxxxxxxx>, "Xen Mailing 
> List" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
> Subject : Re: Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen
> 
> 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
> 
> 
> 

-- 

Whatever you Wanadoo:
http://www.wanadoo.co.uk/time/

This email has been checked for most known viruses - find out more at: 
http://www.wanadoo.co.uk/help/id/7098.htm



-------------------------------------------------------
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