Re: [Xen-devel] [PATCH 05/18] xen/pvcalls: connect to a frontend

2017-05-16 Thread Stefano Stabellini
On Tue, 16 May 2017, Stefano Stabellini wrote: > > > diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c > > > index 86eca19..876e577 100644 > > > --- a/drivers/xen/pvcalls-back.c > > > +++ b/drivers/xen/pvcalls-back.c > > > @@ -44,13 +44,100 @@ struct pvcalls_back_global { > > >

Re: [Xen-devel] [PATCH 05/18] xen/pvcalls: connect to a frontend

2017-05-16 Thread Stefano Stabellini
On Mon, 15 May 2017, Boris Ostrovsky wrote: > On 05/15/2017 04:35 PM, Stefano Stabellini wrote: > > Introduce a per-frontend data structure named pvcalls_back_priv. It > > contains pointers to the command ring, its event channel, a list of > > active sockets and a tree of passive sockets (passing s

Re: [Xen-devel] [PATCH 05/18] xen/pvcalls: connect to a frontend

2017-05-15 Thread Boris Ostrovsky
On 05/15/2017 04:35 PM, Stefano Stabellini wrote: Introduce a per-frontend data structure named pvcalls_back_priv. It contains pointers to the command ring, its event channel, a list of active sockets and a tree of passive sockets (passing sockets need to be looked up from the id on listen, acc

[Xen-devel] [PATCH 05/18] xen/pvcalls: connect to a frontend

2017-05-15 Thread Stefano Stabellini
Introduce a per-frontend data structure named pvcalls_back_priv. It contains pointers to the command ring, its event channel, a list of active sockets and a tree of passive sockets (passing sockets need to be looked up from the id on listen, accept and poll commands, while active sockets only on re