[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] EXPORT SYMBOL for alloc_vm_area

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?



Date: Thu, 19 Jan 2006 19:14:21 +0000
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] EXPORT_SYMBOL for get_vm_area ...
To: Himanshu Raj <rhim@xxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Message-ID: <27575039d47752db8a244204172080c8@xxxxxxxxxxxx>
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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.