From: Jon Mason <jdmason@us.ibm.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: xen-devel@lists.xensource.com, Nick Logan <nick_logan@symantec.com>
Subject: Re: Re: Xen-devel Digest, Vol 11, Issue 86
Date: Wed, 25 Jan 2006 14:26:48 -0600 [thread overview]
Message-ID: <20060125202648.GA6794@us.ibm.com> (raw)
In-Reply-To: <20060125142541.GC24849@granada.merseine.nu>
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
next prev parent reply other threads:[~2006-01-25 20:26 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 ` EXPORT SYMBOL for alloc_vm_area Nick Logan
2006-01-25 14:25 ` Re: Xen-devel Digest, Vol 11, Issue 86 Muli Ben-Yehuda
2006-01-25 20:26 ` Jon Mason [this message]
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=20060125202648.GA6794@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=mulix@mulix.org \
--cc=nick_logan@symantec.com \
--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.