From: Nick Logan <nick_logan@symantec.com>
To: Keir.Fraser@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: EXPORT SYMBOL for alloc_vm_area
Date: Wed, 25 Jan 2006 11:40:59 +0000 [thread overview]
Message-ID: <43D763CB.5070702@symantec.com> (raw)
In-Reply-To: <43D762AB.2010702@symantec.com>
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 <Keir.Fraser@cl.cam.ac.uk>
>> Subject: Re: [Xen-devel] EXPORT_SYMBOL for get_vm_area ...
>> To: Himanshu Raj <rhim@cc.gatech.edu>
>> 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
>>
>>
>>
next prev parent reply other threads:[~2006-01-25 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ezkwr-000797-RL@host-192-168-0-1-bcn-london>
2006-01-25 11:36 ` Xen-devel Digest, Vol 11, Issue 86 Nick Logan
2006-01-25 11:40 ` Nick Logan [this message]
2006-01-25 14:25 ` Muli Ben-Yehuda
2006-01-25 20:26 ` Jon Mason
2006-01-26 9:51 ` EXPORT SYMBOL for alloc_vm_area Nick Logan
2006-01-26 15:37 ` Muli Ben-Yehuda
2006-01-26 15:55 ` Nick Logan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43D763CB.5070702@symantec.com \
--to=nick_logan@symantec.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.