From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [patch 24/26] Xen-paravirt_ops: Add the Xenbus sysfs and virtual device hotplug driver. Date: Fri, 16 Mar 2007 09:57:26 -0700 Message-ID: <45FACC76.1020902@goop.org> References: <20070301232443.195603797@goop.org> <20070301232529.271605211@goop.org> <20070316084704.GB23174@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070316084704.GB23174@elte.hu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ingo Molnar Cc: Zachary Amsden , xen-devel@lists.xensource.com, Ian Pratt , virtualization@lists.osdl.org, Rusty Russell , linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen , Andrew Morton , Greg KH , Christian Limpach List-Id: virtualization@lists.linuxfoundation.org Ingo Molnar wrote: > * Jeremy Fitzhardinge wrote: > > >> This communicates with the machine control software via a registry >> residing in a controlling virtual machine. This allows dynamic >> creation, destruction and modification of virtual device >> configurations (network devices, block devices and CPUS, to name some >> examples). >> > > should be reviewed by the driver-core folks too i guess? > > >> +//#include >> > > >> +//#include >> +//#include >> > > >> +//#include >> > > >> +// .shutdown = xenbus_dev_shutdown, >> > > hm? > Yeah, gunk. I'll clean that out. J