From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Mason Subject: Re: Re: Xen-devel Digest, Vol 11, Issue 86 Date: Wed, 25 Jan 2006 14:26:48 -0600 Message-ID: <20060125202648.GA6794@us.ibm.com> References: <43D762AB.2010702@symantec.com> <20060125142541.GC24849@granada.merseine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060125142541.GC24849@granada.merseine.nu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Muli Ben-Yehuda Cc: xen-devel@lists.xensource.com, Nick Logan List-Id: xen-devel@lists.xenproject.org On Wed, Jan 25, 2006 at 04:25:41PM +0200, Muli Ben-Yehuda wrote: > On Wed, Jan 25, 2006 at 11:36:11AM +0000, Nick Logan wrote: > > It certainly seems that you need all of the functions in > > drivers/xen/util.c, ie alloc_vm_area, free_vm_area, lock_vm_area and > > unlock_vm_area to be exported in order build a loadable xen driver. Can > > these be added? These functions are only needed to build the backend drivers as modules. While this seems like it should be possible, the possibility of removing the backend while frontends exists is a BAD idea and probably should not be possible (unless we have an infrastructure similar to one described by Harry Butterworht). > > Just curious, why do you need loadable Xen drivers? To break Xen in new and interesting ways! Thanks, Jon