Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-02-10 Thread Konrad Rzeszutek Wilk
On Fri, Feb 10, 2017 at 12:09:36PM -0800, Stefano Stabellini wrote: > On Fri, 10 Feb 2017, Konrad Rzeszutek Wilk wrote: > > .snip.. > > > > > Request fields: > > > > > > > > > > - **cmd** value: 0 > > > > > - additional fields: > > > > > - **id**: identifies the socket > > > > > - **addr**: ad

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-02-10 Thread Stefano Stabellini
On Fri, 10 Feb 2017, Konrad Rzeszutek Wilk wrote: > .snip.. > > > > Request fields: > > > > > > > > - **cmd** value: 0 > > > > - additional fields: > > > > - **id**: identifies the socket > > > > - **addr**: address to connect to, see [Socket families and address > > > > format] > > > > > >

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-02-10 Thread Konrad Rzeszutek Wilk
.snip.. > > > Request fields: > > > > > > - **cmd** value: 0 > > > - additional fields: > > > - **id**: identifies the socket > > > - **addr**: address to connect to, see [Socket families and address > > > format] > > > > > > Hm, so what do we do if we want to support AF_UNIX which has an a

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-02-09 Thread Stefano Stabellini
On Tue, 7 Feb 2017, Konrad Rzeszutek Wilk wrote: > .snip.. > > Frontend XenBus Nodes > > > > version > > Values: > > > > Protocol version, chosen among the ones supported by the backend > > (see **versions** under [Backend XenBus Nodes]). Currently the > > value

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-02-07 Thread Konrad Rzeszutek Wilk
.snip.. > Frontend XenBus Nodes > > version > Values: > > Protocol version, chosen among the ones supported by the backend > (see **versions** under [Backend XenBus Nodes]). Currently the > value must be "1". > > port > Values: > > The identi

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-01-29 Thread Oleksandr Andrushchenko
On 01/27/2017 08:48 PM, Stefano Stabellini wrote: On Fri, 27 Jan 2017, Oleksandr Andrushchenko wrote: Hi, Stefano! Error numbers The numbers corresponding to the error names specified by POSIX are: [EPERM] -1 [ENOENT]-2 Don't you want to use Xen's errno.h

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-01-27 Thread Stefano Stabellini
On Fri, 27 Jan 2017, Oleksandr Andrushchenko wrote: > Hi, Stefano! > > Error numbers > > > > The numbers corresponding to the error names specified by POSIX are: > > > > [EPERM] -1 > > [ENOENT]-2 > > > Don't you want to use Xen's errno.h here as described in [1]? >

Re: [Xen-devel] [DOC v8] PV Calls protocol design

2017-01-26 Thread Oleksandr Andrushchenko
Hi, Stefano! Error numbers The numbers corresponding to the error names specified by POSIX are: [EPERM] -1 [ENOENT]-2 Don't you want to use Xen's errno.h here as described in [1]? So we have error codes consistent for all PV protocols? Thanks, Oleksandr [1] ht

[Xen-devel] [DOC v8] PV Calls protocol design

2017-01-24 Thread Stefano Stabellini
Changes in v8: - introduce the concept of indexes page - many clarifications - add a diagram - introduce support for multiple versions of the protocol Changes in v7: - add a glossary of Xen terms - add a paragraph on why Xen was chosen - wording improvements - add links to xenstore documents and