Re: [Xen-devel] xenbus_backend_client.c / xenbus_client.c merger

[Keir Fraser <keir@xxxxxxxxxxxxx>]

On 19/2/07 14:00, "Kieran Mansley" <kmansley@xxxxxxxxxxxxxx> wrote:

> Although I don't know the full history, it looks like at some point
> linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_backend_client.c was
> created to hold "backend only" code that would otherwise be in
> linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_client.c.
> 
> However, the code in xenbus_backend_client.c isn't currently specific to
> the backend - it just happens to be that no frontends use it.  At least
> that's how it looks to me.

Currently we have a model that frontends supply memory for ring buffers,
which backends map into their kernel address space. Where is the memory
coming from that your frontend maps? Is it appropriate to be using grant
table entries to refer to and map that memory?

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel