[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

No, not fundamentally true.  The registry approach decouples the
generation of the hotplug events from the provider of devices such that
if the domain hasn't booted yet then the provider of devices doesn't
care: the registry will generate all the required hotplug events when
the domain connects after it boots.

As an aside, my previous messages were breaking threading so I changed
from the web based email to Evolution. Should be OK now.

On Tue, 2005-03-01 at 00:32 +1100, Rusty Russell wrote:
> On Mon, 2005-02-28 at 14:08 +0100, harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> wrote:
> > 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?
> Fundamentally true, because you can't send a hotplug event to a domain
> which hasn't been booted yet.  Whatever your mechanism, the this
> difference has to be handled at some level, and I don't think the
> difference in transport makes it harder.
> Cheers,
> Rusty.

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.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.