From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Logan Subject: EXPORT SYMBOL for alloc_vm_area Date: Wed, 25 Jan 2006 11:40:59 +0000 Message-ID: <43D763CB.5070702@symantec.com> References: <43D762AB.2010702@symantec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43D762AB.2010702@symantec.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir.Fraser@cl.cam.ac.uk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Sorry, sent too soon, have changed title and deleted unneccessary text 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? > > Thanks, > > Nick > >> Date: Thu, 19 Jan 2006 19:14:21 +0000 >> From: Keir Fraser >> Subject: Re: [Xen-devel] EXPORT_SYMBOL for get_vm_area ... >> To: Himanshu Raj >> Cc: xen-devel@lists.xensource.com >> Message-ID: <27575039d47752db8a244204172080c8@cl.cam.ac.uk> >> Content-Type: text/plain; charset=US-ASCII; format=flowed >> >> >> On 16 Jan 2006, at 05:34, Himanshu Raj wrote: >> >> >> >>> Hi Folks, >>> >>> To build drivers externally using >>> linux-2.6-xen-sparse/drivers/xen/util.c, >>> I need the symbols get_vm_area and remove_vm_area exported (they >>> were exported >>> previously - not any more in the latest version). >>> >>> Am I missing something here? >>> >> >> >> Do you mean alloc_vm_area and free_vm_area? get/remove_vm_area >> shouldn't be getting directly referenced from our driver modules. >> >> -- Keir >> >> >>