From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Proposal for init/kexec/hotplug format for Xen Date: Mon, 28 Feb 2005 09:46:41 -0600 Message-ID: <42233CE1.4010906@us.ibm.com> References: <1109451460.32219.11.camel@localhost.localdomain> <68d3daa4e95f4ba6740c6c0ffd3f67b8@cl.cam.ac.uk> <4221E676.5000008@us.ibm.com> <1109592413.7090.11.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <1109592413.7090.11.camel@localhost.localdomain> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Rusty Russell Cc: Keir Fraser , Jeremy Katz , Xen Mailing List List-Id: xen-devel@lists.xenproject.org I have a few questions about some of the future features: 1) What is the transport going to be for querying/updating? How are you going to handle security? 2) Are we going to use any sort of standard for storing device information? If so, what? 3) How does this change the device setup exchange? Right now, a series of control messages is exchanged so that the back-end can get notified to create the virtual device and then something has to proxy some information from the front-end (usually just a shared memory location) to that backend. All of this is still necessary right? How does a value being updated trigger an appropriate event? Regards, Anthony Liguori >Included below for your reading pleasure, >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. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click