From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: [patch 24/26] Xen-paravirt_ops: Add the Xenbus sysfs and virtual device hotplug driver. Date: Fri, 16 Mar 2007 09:18:04 -0700 Message-ID: <20070316161804.GH10574@sequoia.sous-sol.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: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20070316084704.GB23174@elte.hu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.osdl.org Errors-To: virtualization-bounces@lists.osdl.org To: Ingo Molnar Cc: xen-devel@lists.xensource.com, Ian Pratt , linux-kernel@vger.kernel.org, Chris Wright , virtualization@lists.osdl.org, Andrew Morton , Greg KH , Andi Kleen List-Id: virtualization@lists.linuxfoundation.org * Ingo Molnar (mingo@elte.hu) 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? Greg has gone through it a couple times. Any more feedback would be useful. > > +//#include > = > > +//#include > > +//#include > = > > +//#include > = > > +// .shutdown =3D xenbus_dev_shutdown, > = > hm? fixing that up, not sure where that snuck in.